Prune unused Cartesian axes before rendering - #636
Open
rosenrot00 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
xaxisandyaxisThe current defaults materialize up to 30 X-axis and 30 Y-axis layout entries for every card. Plotly processes all of them on every
react(), even when a simple chart only uses one X and one Y axis.Pruning after configuration evaluation is important because entity axis assignments can be dynamic or derived from units. At that point all
$fnvalues and automatic Y-axis assignments are known, so unused defaults can be removed without guessing.The integration test verifies that a simple parsed chart keeps exactly
xaxisandyaxis. Explicit YAML and preset axes, trace references, layout references, and axis-to-axis references remain intact.