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.
This is on top of #2774, to avoid churning the snapshot tests (since that PR has some styling changes with wider impact, and this one does with adjusting thresholds).
Who is this PR for?
MTSS facilitators, reading specialists, literacy coaches, K5 classroom teachers
What problem does this PR fix?
This came up with literacy coaches, and so there are some slight revisions to the benchmarks here, but the main intention was to pick these for each of the screening time periods, and extend them out to fifth grade as well. That way if there's screening, there's a way to support highlighting these as well.
What does this PR do?
Updates the thresholds, and then some styling for
<ReadingScheduleGrid />
, which is used for visualizing the thresholds, and the full raw set of data points over time. Both are intended more for validating data, but the substantive change is that the highlighting in the reader profile will change to match these thresholds. We'll validate this with folks looking at the overall distributions for different cohorts, particularly after this next interval.Screenshot (if adding a client-side feature)
Checklists
Which features or pages does this PR touch?
Does this PR use tests to help verify we can deploy these changes quickly and confidently?