Repository navigation
docs: explain optional props absent from known callers - #85
Merged
Merged
Conversation
BartWaardenburg
force-pushed
the
feat/absent-component-props
branch
from
October 5, 2026 17:52
6509453 to
4595621
Compare
BartWaardenburg
force-pushed
the
feat/absent-component-props
branch
from
October 5, 2026 19:34
4595621 to
5142847
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
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.
Explain the opt-in
absent-component-propsrule: optional inputs read locally but omitted by every inspected reachable caller. Document declaration and caller evidence, defaults, explicit supplied values, static caller completeness and manual-only actions.Add the rule and selector to configuration, CLI and MCP references. Describe supported syntax and uncertainty boundaries for all modeled component framework families.
Validation: content manifest, repository checks, heading anchors and source/output fact checks pass. The public Card example was executed against the implementation.