This repository has been archived by the owner on Nov 4, 2024. It is now read-only.
feature/COR-1269-time-series-chart-y-axis-scaling #4551
Merged
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.
Summary
Motivation
The aforementioned pull request introduced a new
minimumRange
property to all time series charts default to a value of10
, yet also took the chart representing the R-number into account (which should hopefully never come anywhere near 10). However, this same pull request does not take charts into account in certain (possibly less visited) pages around the dashboard. Examples of these charts are in the list below. Rather than adding an override forminimumRange
to all these pages/charts, I opted to investigate if we could revert the introduction ofminimumRange
. After this revert, and as such before the merge of the above pull request, all time series charts will use their OOTB logic to dynamically scale its y-axis based on the highest value inside the range of the series, meaningminimumRange
can be completely omitted.Examples of pages/charts that are affected by the introduction of
minimumRange
include but are not limited to: