DateTimePicker - Implement renderInput prop #1352
Closed
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
The renderInput prop was missing, it was mentioned in the documentation however wasnt used in the code.
Amurmurmur
changed the title
Amurmurmur
changed the title
|
Hi @Amurmurmur Closing this. |
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.
The renderInput prop was missing, it was mentioned in the documentation however wasnt used in the code.
Description
The renderInput prop wasnt used in the codebase for the DateTimePicker, however it was mentioned in the documentation therefore it wasn't able to let the user to provide with their own custom input component instead of a default TextField
Changelog
Abillity to use renderInput prop with the DateTimePicker component that was missing.