Use imported mixin type in ItemSet and OptionSet - #79
Merged
tajakobsen merged 1 commit intoSep 14, 2026
Merged
Conversation
If the only form field in an item-set, or in an option of an option-set, is a mixin, reference the type generated for the mixin instead of inlining its fields. The import path is computed relative to each generated file. Closes #76
tajakobsen
deleted the
76-use-import-type-for-mixin-when-only-child-in-option-set
branch
September 14, 2026 09:25
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
1 participant
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.
If the only form field in an item-set, or in an option of an option-set, is a mixin, reference the type generated for the mixin instead of inlining its fields. The import path is computed relative to each generated file.
Closes #76