[docs] Add missing props to *DatePicker API #25254
Merged
Conversation
This file contains 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.
yarn proptypesis incomplete if files are used that can't be parsed by TypeScript 3.5.import typeis one of those things.I haven't figured out how to throw if these diagnostics affect
yarn proptypesso for now we have to do it manually (as documented in code).We could lint against it with
no-restricted-syntaxandImportDeclaration[importKind="type"]but eslint rules can only be overridden not extended and I don't want to spend an hour digging through all the configs we have to find out what we currently lint against.