Feature: figure semantic legends#707
Open
cvanelteren wants to merge 3 commits intomainfrom
Open
Conversation
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
gepcel
approved these changes
Apr 30, 2026
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
2 participants
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 #706
This exposes the public API for adding semantic legends to the figure class. This PR is a shallow pass however.
Currently UltraPlot has an awkward split on the semantic legends under
UltraLegendand the actual thin matplotlib wrapper for the implementation of the legend underLegend. A future refactor would need to integrate these two either through composition to reduce the overhead. It ties closely into a general refactor for theFigureclass in general but is important to note regardless.A follow-up refactor should separate semantic legend content generation from legend placement and rendering. The likely direction is a composition-based design with target-agnostic builders that return
(handles, labels), and thinAxesandFigureadapters that place those legends through their respective public APIs.