fix(www): propstable resolve props properly#4304
Merged
Merged
Conversation
|
Contributor
|
Preview deployments for this pull request: www - |
Barsnes
approved these changes
Dec 10, 2025
Member
Barsnes
left a comment
There was a problem hiding this comment.
Awesome work! Let's merge this and get it deployed.
We can fix up types before the next release :)
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
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.
react-docgen-typescriptwas being fed the wrong tsconfig, the correct one in this context istsconfig.lib.json.Missing propstables like Dropdown and TextField are now included.
The side effect of this is we now get a lot "more" types, for example
Suggestionget types forSuggestionClearandSuggestionInputwhich is justButtonandInput. Not sure if we should do something about stuff like that.