Repository navigation
[scheduler] Add localeText prop to standalone views - #23210
Merged
rita-codes merged 8 commits intoJul 24, 2026
Merged
rita-codes merged 8 commits into
rita-codes merged 8 commits into
Conversation
…View Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DTQDtignuUE3UECjCEHozo
Threads the localeText prop through StandaloneDayView, StandaloneMonthView, StandaloneAgendaView, StandaloneCompactDayView, StandaloneCompactThreeDayView, and StandaloneCompactWeekView, following the pattern established for StandaloneWeekView, so these standalone views can be localized. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DTQDtignuUE3UECjCEHozo
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DTQDtignuUE3UECjCEHozo
Regenerates the propTypes blocks and API docs JSON/translations for the standalone views affected by the new `localeText` prop added in the preceding commits, and applies a prettier fix to EventCalendarProvider. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DTQDtignuUE3UECjCEHozo
rita-codes
added
type: bug
…pose-a-localetext-prop
Deploy previewBundle size
Check out the code infra dashboard for more information about this PR. |
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DTQDtignuUE3UECjCEHozo
…text-prop' of github.com:rita-codes/mui-x into 23116-scheduler-standalone-views-do-not-expose-a-localetext-prop
rita-codes
requested review from
flaviendelangle and
noraleonte
and removed request for
noraleonte
July 23, 2026 17:31
…pose-a-localetext-prop
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
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.
Fixes #23116
All standalone views mounted their styled contexts through the internal
EventCalendarProvider, which hardcodedEVENT_CALENDAR_DEFAULT_LOCALE_TEXT, so there was no way to localize them. This PR adds alocaleTextprop to that shared provider (merging with the defaults, same pattern asEventCalendar) and threads it through all 11 standalone views (7 community + 4 premium), declaring it on eachStandalone*ViewPropstype with the same JSDoc asEventCalendar.Standalone views now also resolve theme default props via
useThemePropswith the shared'MuiEventCalendar'key (same key sharing asEventCalendarPremiumand the Data Grid family), so locale packs applied through the theme (createTheme({}, esES)) reach them too, with thelocaleTextprop taking precedence over the theme.Added unit tests for
StandaloneWeekViewandStandaloneWeekViewPremiumcovering the prop, the theme mechanism, and prop-over-theme precedence. PropTypes and API docs regenerated — note the 3 compact views are intentionally excluded from generation by the pre-existingCOMPONENTS_WITHOUT_PROPTYPESlist, so only the 8 public views got propTypes/docs entries. ThethemeDefaultPropsconformance test stays skipped for standalone views: their wrapper elements don't forward arbitrary props tocontainer.firstChild, so the assertion can't apply structurally — theme resolution is covered by the new unit tests instead.