-
Notifications
You must be signed in to change notification settings - Fork 355
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
enforceMinMax on stacked guages #3918
Comments
Hi @Sebastian-medilingua, as you stated Thanks for the suggestion. |
Hi @netil, though that would be nice, I think the documentation is still a bit unclear right now and probably should be updated. as you can see other items contain limitations and notes but enforceMinMax doesn't. Could it be updated whilst the enhancement is in consideration? |
Currently enforceMinMax option works for single data series only. Make sure clarifying the use of this option Ref naver#3918
Currently enforceMinMax option works for single data series only. Make sure clarifying the use of this option Ref #3918 Co-authored-by: netil <netil@AD02298065.local>
Currently enforceMinMax option works for single data series only. Make sure clarifying the use of this option Ref #3918
Updated the doc clarifying the option works for single data series only. |
Description
I'm trying to create a gauge which shows 3 categories stacked together whilst the max is enforced to a set value. But it doesn't stack then. I can understand why this is, but it makes it hard to figure out why it happens. It feels as if its a bug even though in the code there is clearly a check for it
https://github.com/naver/billboard.js/blob/744c4fdfc0a75b1bb965b2a6d2d861cb6bea6801/src/ChartInternal/shape/arc.ts#L335C3-L344C4
Could it be made more clear that enforceMinMax is currently only for unstacked/multi gauges?
Would it be possible to have it so that data can be stacked and have a limit? (Or is that not possible)
Steps to check or reproduce
https://jsfiddle.net/357rLq90/2/
(what I intended was that received and expected are fully shown and due being only partially shown but the labels displaying the correct value)
The text was updated successfully, but these errors were encountered: