Add support for avar2 <mappings> element #383
Merged
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
cmyr
approved these changes
Jan 14, 2026
Member
cmyr
left a comment
cmyr
left a comment
There was a problem hiding this comment.
Looks good, one little question inline but otherwise happy to get this merged. :)
Member
|
@simoncozens would you like a release? |
Contributor
Author
|
Sure! Thanks! |
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.
This adds support for the avar2
<mappings>element which lives inside of<axes>. This of course means that<axes>is no longer a pureVec<Axis>, which means we have to do some shenanigans to support the new element and maintain the existing API.#[serde(from..., into...)]provides the shenanigans, and we add a separate top-levelaxis_mappingsfield.