Render dashboard date time fields in the configured display timezone - #439
Merged
Merged
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
The timezone configured via the Timezone setting under Manage Localization only affected the public status page; the dashboard kept rendering and accepting date time fields in the application timezone, so the same instant appeared inconsistently and was confusing.
When the panel boots, it now reads the timezone setting and applies it as Filament's global timezone. This happens through a closure, so the setting isn't read until the database is actually available. Filament then handles the conversion in both directions: tables and infolists display dates in that timezone, and DateTimePicker values are converted back to the app timezone before saving, so nothing changes about how dates are stored.
Note that since the "-" (browser default) sentinel cannot be resolved server-side, the dashboard falls back to the application timezone in that case.
Closes #262