Don't use offset / scientific notation in numeric legends #3187
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.
Fixes #3174:
This takes the shortest path solution of simply disabling the offset / scientific notation on a scalar formatter used in the legend. I think it's possible that we'll want to add those as options in
Continuous.label
in which case we may want to figure out how to show the extra information in a legend context (e.g. as a subtitle or extra row at the bottom of the legend). Punting on that as it seems complicated.Note that if you do want to format legend entries with scientific notation, you can do
Continuous().label(like="{x:.2g}")
(not exactly the same thing, but will help when variables have very large values).