fix: restore native Date fallback when strictParsing is false #6172
+75
−1
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
strictParsingis false (the default), flexible input formats like12/05/2025or2025-12-16 3:31:01 PMare now parsed even when thedateFormatprop specifies a different formatProblem
In v8.0.0, the
parseDatefunction was refactored and the nativenew Date(value)fallback was removed. This caused a regression where users could no longer type dates in flexible formats - only exact matches to thedateFormatprop were accepted.Before v8 (working):
v8.0.0+ (broken):
Solution
Add back the native Date fallback when
strictParsingis false. The fallback only triggers when:strictParsingis false (default)Test plan
Fixes #6164
🤖 Generated with Claude Code