[DatePicker] Fix Input not clear for invalid date #29071
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
Author
|
@eps1lon Please let me if any changes are required in PR. |
mbrookes
added
component: DatePicker
Member
|
Thank you for your contribution. |
|
Hi, Can this PR be kept to fix the bug until the rework is complete? It solves an issue that is currently happening. Thanks. |
Member
|
@mnajdova if you want to merge it 👍 |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Closes: mui/mui-x#4870
In
useMaskedInput hookwhen there is invalid date so current value is set to empty""string. then it check is valid changed or not. that's why value is not set to clear after invalid date.I added another check for
rawValueand check if rawValue change or not. If yes then set new value.