Fixed Digit Date Token Shape Parser
Parse fixed-width YYYY-MM-DD token shape only; intentionally preserves invalid calendar component values as unvalidated evidence.
Description
Parse fixed-width YYYY-MM-DD token shape only; intentionally preserves invalid calendar component values as unvalidated evidence.
A date-shaped token is not necessarily a valid calendar date. This parser deliberately exposes shape without calendar validation.
When to use this tool
Parse fixed-width YYYY-MM-DD token shape only; intentionally preserves invalid calendar component values as unvalidated evidence.
- Prepare the supplied token fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter token. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.year, result.month, result.day, result.calendarValidated. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require exactly four digits, dash, two digits, dash and two digits. Return numeric year, month and day, with calendarValidated always false.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| token | token. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.year | The year value under the stated formula or text convention. |
| result.month | The month value under the stated formula or text convention. |
| result.day | The day value under the stated formula or text convention. |
| result.calendarValidated | Always false; this parser checks the digit shape rather than calendar validity. |
{
"input": {
"token": "2026-99-00"
},
"output": {
"result": {
"year": 2026,
"month": 99,
"day": 0,
"calendarValidated": false
}
}
}Limitations and assumptions
- Values such as month 99 and day zero pass the shape check. Leap years, actual dates, timezones and chronology are not validated.
- All declared input fields are required and unexpected top-level fields are rejected. Numbers must be finite; lists are limited to 128 entries and ordinary text fields to 8,192 UTF-16 code units, with tighter limits where stated.
- JSON text inputs must parse within bounded nesting and size limits. Numeric outputs outside the safe finite range are rejected; large exact integer results use decimal strings. Indexes and half-open spans are zero-based unless a rank is explicitly described as one-based.
Alternative or Complementary methods
Use a parser for the actual target format when the task requires CSV, shell, URL, calendar or filesystem semantics. These tools implement the specific small grammars stated here, without adding those surrounding conventions.
References
Similar or alternative tools
- Balanced Parenthesis Token Splitter
Split a literal delimiter only outside balanced parentheses; parentheses are retained, quotes and escapes have no special meaning.
- date
Parse a calendar date in an explicit format into normalized date fields.