-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] [MER-3873] Likert activity for instructors #5274
[FEATURE] [MER-3873] Likert activity for instructors #5274
Conversation
…w ActivityHelpers
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can probably land this as is, but we need to file another ticket (and prioritize) for the work to move away from the resource hierarchy querying.
|
||
def get_activities(assessment_resource_id, section_id, student_ids, filter_by_survey \\ false), | ||
do: | ||
Core.get_evaluated_activities_for( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a really nice isolation of redundant code that had been spread across Practice, Summative and Survey views. But we really should be taking this opportunity to move away from querying across ActivityAttempt and ResourceAttempt tables. Instead, this information can be much more efficiently retrieved by querying across Summary tables and then joining to the corresponding SectionResource record (through section id and resource id) to get the title of the resource.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I filed https://eliterate.atlassian.net/browse/MER-4066 for this future work.
Link to the ticket
Different likert activities (with different amount of questions and options, even different text length for the options) rendered correctly in :
Screen.Recording.2024-11-29.at.2.58.40.PM.mov
This PR sets the ground for rendering light/dark Vegalite Visualizations that react to changes made by the user in the mode selected ("dark", "light", "auto"). Changes can be seen on
assets/src/components/misc/VegaLiteRenderer.tsx
Some refactoring
While working on this feature I found that three tabs (Scored Activities, Practice Activities and Surveys) from the Insights instructor view had duplicated code. So, this PR exctracts common logic of those 3 live_component modules (OliWeb.Components.Delivery.{PracticeActivities, ScoredActivities, Surveys}) into a new
OliWeb.Delivery.ActivityHelpers
module.And some ecto queries from that migrated code where moved to their corresponding context module as well (
Oli.Analytics.Summary
andOli.Delivery.Attempts.Core
)