fix: Make prop-drilling host components configurable#13
Merged
Conversation
ColumbusLabs
approved these changes
Jun 1, 2026
Owner
ColumbusLabs
left a comment
ColumbusLabs
left a comment
There was a problem hiding this comment.
Looks good to me. CI is green on Node 20 and 22, and I also verified locally with npm run test:all, npm run schema:generate, and an end-to-end config smoke test that propDrilling.ignoreComponents suppresses only the prop-drilling finding for the configured component.
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.
Summary
These custom components will be treated as host primitives and won't trigger prop-drilling warnings when props are forwarded to them
Validation