-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Reformat probabilistic numbers in tooltip #435
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
Looks good to me,
The numbers look correct.
Just want to double check something, if there are no PLevels now, does the UI fail?
I wonder if the ttxt should be P90 and P10 not 90% and 10% as this is a bit more recognisable that this is a plevel |
hey @peterdudfield , Thanks for the feedback. I agree that the If there are no values for the plevels, it'll just return nothing. |
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.
Couple of tiny things but then good to merge @rachel-labri-tipton, nice work 😊
Pull Request
Description
Updates the formatting for probabilistic numbers in the tooltip. This was discussed here: #384 .
The updated tooltip looks like this.
It might be noticeable that the
OCF Forecast
is now in semi-bold because thetextClass
applied wasn't working, so I fixed that as well when I set thetextClass
for the P levels and values.I updated
useFormatChartData
so that it returns 3 probabilistic things:PROBABILISTIC_RANGE
as an array for the area plotted on the chart and thenPROBABILISTIC_UPPER_BOUND
andPROBABILISTIC_LOWER_BOUND
as numbers. This seems repetitive, but when it came to the tooltip, it was easy to just have number values for all tooltip labels.In terms of review, would like to know if all tooltip numbers are still showing correctly.
Fixes #384
How Has This Been Tested?
I ran the code locally.
Checklist: