[scheduler] Throw on invalid event dates instead of emitting NaN timestamps#22740
Merged
Conversation
…stamps Malformed `start`/`end`/`exDates` strings flowed through the whole pipeline without validation, producing a `timestamp: NaN` that silently corrupted sorting, positioning, and overlap calculations. Events would vanish or render in absurd positions with no hint of what went wrong. `resolveEventDate` now validates the resolved date with `adapter.isValid()` and throws a descriptive `MUI X Scheduler:` error naming the offending event id and value, so the problem surfaces immediately. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
rita-codes
added
type: enhancement
…ocessed-silently-as-nan-timestamps
Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
Deploy previewBundle size
Check out the code infra dashboard for more information about this PR. |
noraleonte
approved these changes
Jun 12, 2026
noraleonte
left a comment
noraleonte
left a comment
Contributor
There was a problem hiding this comment.
Thanks for fixing this! 🎉
…ocessed-silently-as-nan-timestamps
rita-codes
enabled auto-merge (squash)
June 12, 2026 09:44
…ocessed-silently-as-nan-timestamps
…ocessed-silently-as-nan-timestamps
rita-codes
disabled auto-merge
June 12, 2026 13:04
…ocessed-silently-as-nan-timestamps
mbrookes
pushed a commit
to mbrookes/mui-x
that referenced
this pull request
Jun 27, 2026
…stamps (mui#22740) Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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 #22734
The problem
When an event has a malformed
startorenddate, the value flows through the entire processing pipeline without validation.adapter.date(value)is never checked withadapter.isValid(), soprocessDateends up emittingtimestamp: NaN.A
NaNtimestamp silently corrupts sorting, positioning, and overlap calculations. The affected events either vanish from the view or render in absurd positions, with no error or warning to indicate what went wrong.The fix
resolveEventDatenow validates the resolved date withadapter.isValid()and throws a descriptiveMUI X Scheduler:error naming the offending event id and the invalid value, so the problem surfaces immediately instead of corrupting downstream calculations.The
eventIdargument is optional so the internal callers that resolve dates without an event in scope (e.g.rrule.until, test builders) keep working — the pipeline path (start/end/exDates) always supplies it.