docs: type inference issue on exposed API documentation #21278
Merged
Conversation
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
Components that have exposed reference of VTextField and consequently input are infering HTMLInputElement props, which should not not be documented. This change will filter out these irrelevant props through type.
eesayas
changed the title
eesayas
changed the title
eesayas
changed the title
MajesticPotatoe
approved these changes
Apr 16, 2025
johnleider
approved these changes
Apr 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Description
CleanHTMLInputElementwill filter out nativeHTMLInputElementinferred props. Currently, these components are the ones that usesVTextField(and consequently aninput, where the native props are coming from)Markup:
N/A