Added textual date parsing section. #676
Open
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
EHandtkeBasis
requested review from
MatthewHawkins,
bbrennanbasis,
gosteenBASIS,
hyyan and
laurenic0l
as code owners
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
|
||
| ### Day name decoration {#day-name-decoration} | ||
|
|
||
| Day-of-week names can be included in the input for better readability, but they are **decorative only** and are stripped during parsing. They don't affect the actual date value. |
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Google.Contractions] Use 'they're' instead of 'they are'.
|
|
||
| ### When disabled (default) | ||
|
|
||
| If textual date parsing is **not** enabled (the default behavior), text names will not be recognized: |
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Google.Contractions] Use 'isn't' instead of 'is not'.
|
|
||
| ### When disabled (default) | ||
|
|
||
| If textual date parsing is **not** enabled (the default behavior), text names will not be recognized: |
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Google.Contractions] Use 'won't' instead of 'will not'.
hyyan
added
the
status: waiting-for-review
MatthewHawkins
requested changes
Jan 5, 2026
|
|
||
| ## Textual date parsing {#textual-date-parsing} | ||
|
|
||
| By default, the `MaskedDateField` only accepts numeric input for dates. However, you can enable **textual date parsing** to allow users to enter month and day names in their input. This feature is particularly useful for creating more natural date entry experiences. |
Member
There was a problem hiding this comment.
Remove "experiences" at the end, and just end with "entry".
|
|
||
| #### Examples | ||
|
|
||
| | Mask | Input | Result | |
Member
There was a problem hiding this comment.
In all of the tables, please remove the check emojis at the end
| | `%Dz/%Ml/%Yz` | `01/September/25` | ✅ Valid - Parses as September 1, 2025 | | ||
| | `%Ms/%Dz/%Yz` | `09/01/25` | ✅ Valid - Numeric fallback still works | | ||
|
|
||
| All 12 months are supported in both short (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec) and long (January, February, etc.) forms. |
Member
There was a problem hiding this comment.
This seems like a good candidate for a tip
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.
No description provided.