fix(typing): Support any valid number for utility props that needs it #357
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
Based on the code itself and the website, some declarations don't match the actual typing of some props.
For instance, sizing props such as
w
/h
or evenborder
/borderWidth
should accept any valid number (not only the numbers defined in the theme)."Any valid value is accepted in width, numbers are converted to px, other units have to be specified."
So, I went through all the exposed props and I've updated the typing to add the missing valid type which is
number
in this case.