fix: new approach to generate learner_state_count
in admin assignments list API; add addtl ordering and filtering support
#324
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
content_quantity
can be used with?ordering
.learner_state
("Status" column) can be filtered by one or more values at a time (e.g.,learner_state=waiting
,learner_state=notifying,failed
).learner_state_counts
is generated to no longer rely on.values('learner_state').annotation(count=Count('uuid', distinct=True))
, which seems to be causing the exception seen in the following screenshot locally (not in stage/prod, though?). API now relies onCounter
to determine the counts of eachlearner_state
. It also now ensuresself.filter_queryset()
is called before generating these counts.