More reliable MakieOutput #263
Open
Conversation
This file contains 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.
In this PR I'm hoping to fix a bunch of things with the MakieOutput to standardise workflows so things mostly just work.
First, the objects returned as frames should always be the identical typed. This is so that lift works with no bugs.
Second, we should also always rebuild any AbstractDimArray instead of passing a raw grid through to any showframe method.
Possibily, we should just use DimArray everywhere internally... but that has some compilation and complexity overheads. Maybe we can just rewrap them for any GridRule and output where users should actually interacti with the whole array rather than a single cell.