Feat/format sequence labels - #817
Draft
cvanelteren wants to merge 11 commits into
Draft
Conversation
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
cvanelteren
force-pushed
the
feat/format-sequence-labels
branch
from
September 4, 2026 06:19
5abf152 to
ceba128
Compare
Collaborator
Author
|
This is now combining a few different issues. One being a refactor of We maintain the same sharing levels, but add option for disconnecting sharing limits and labels. Indexing to axis may remove sharing if limits are reset. This creates a stronger identity on the subplotgrid and the individual axes. The subplotgrid can be used to delegate the formatting or plotting, whereas setting particular things that should be shared on index axes, will stop the sharing. Intention of the user is trusted here. |
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.
Closes #815
By default ultraplot shares axes which is great but creates an awkward setup when forcing everything through format. Especially for newer users. Suppose we want to make an axis in a usually 2x2 grid, we write:
If we then want to format the titles, we can do so with
However, say a novice reader would also like to setup xlabels separately (for whatever reason) then this will not work
It will spit out ["a", "b", "c", "d"] on the shared axes -- this seems silly. I think what we should instead assume is that the user wants to put a, b, c, d as xlabels for each axes. This implies two things. First, the sharing level would need to be auto adjusted. Second, we need to parse and pass this across the axes. Limits are still shared as usual (unless passed on as well).
This warrants therefore a separate (and new) sharing level where de decouple labels and limits.
So we have a couple of new situations
Behind the scenes it will add new bools to make label and tick sharing independent. Overrides can be provided by new api key words
The sharing levels are not changed (maybe we should?)
It also adds dict parsing for inputs so we can set directly a particular axis, i.e.