VariationModel only needs to know the axis order#1686
Merged
Conversation
anthrotype
reviewed
Oct 8, 2025
anthrotype
reviewed
Oct 8, 2025
Instead of needing to fully own a copy of the `Axes` struct. - this will simplify using the variation model for the mini design spaces used by smart components - this means there is only one copy of 'Axes', which lives in StaticMetadata - overall this makes it easier to construct a VariationModel.
cmyr
force-pushed
the
varmodel-axis-order
branch
from
bf95688 to
5771a1c
Compare
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.
Instead of needing to fully own a copy of the
Axesstruct.