Clean up prop types definitions for top-level components #332
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.
This change does the following
onDate(s)Change
andonFocusChange
requiredDateRangePicker
,SingleDatePicker
,DayPicker
by category with commentsforbidExtraProps
on all componentsI would like ideally to have
focusedInput
/startDate
/endDate
andfocused
/date
to be required as well, but since those can take a value ofnull
that's a bit trickier. I might make a validator that allows for this (something likeisDefined
).to: @airbnb/webinfra