Repository navigation
declare and check the DFN fields mixins use - #447
Merged
Merged
Conversation
wpbonelli
commented
Oct 10, 2026
wpbonelli
commented
Member
- declare the DFN fields each mixin uses
- fail sync if the DFNs lack one
Each mixin lists the DFN fields it uses in _requires, and check_mixins fails a sync to DFNs missing any of them, naming the mixin, component and fields, before anything is written. It reads _requires from the source rather than importing the mixin, since that can import generated modules. A test keeps the declarations honest: every DFN field a mixin reads off self must be declared. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.