Fix hard coded informations (timezone and orgId) #4056
Merged
Conversation
This file contains 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
✅ Deploy Preview for teslamate ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
@DrMichael perhaps it is intended to leave these "timezones" hard? |
|
No, don't think so. I am fine with that change, we will see. |
|
Good spot! With #4064 we enable browser based time settings. |
JakobLichterfeld
approved these changes
Jul 8, 2024
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.
I noticed that the timezone was hard in 2 dashboards
The browser is the default behavior: https://grafana.com/docs/grafana/latest/administration/organization-preferences/#change-the-grafana-default-timezone
On the other hand, by forcing it, overrides (coming from the server, organization, team, or individual user level) are not taken into account.