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.
Description
@max_consecutive_assessments
Motivation and Context
With the recent Rails upgrade, in
risk_condition#get_current_for_course
,RiskCondition.where(course_id: course_id, version: max_version)
now returns aHash
instead ofHashWithIndifferentAccess
. Hence, we can no longer use symbols interchangeably with strings as keys. This PR modifies the Hash accesses to use string keys.Furthermore, since consecutive assessments are inclusive, we should not subtract one when calculating
@max_consecutive_assessments
, else we can't set the grades dropping metric to cover all assignments.How Has This Been Tested?
Tested workflow for metrics improvement.
Essentially, define categories of 2 assignments to test the following metrics (and considered categories feature)
Tips and reminders
due_date ASC
Types of changes
Checklist:
overcommit --install && overcommit --sign
to use pre-commit hook for linting