We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
At the moment, we only have one global timezone setting for the cms. In some cases, we might have regions of different timezones in the same database.
request.region
This is a precondition of #663 and probably makes #662 obsolete.
The text was updated successfully, but these errors were encountered:
2022.4.2
JoeyStk
Successfully merging a pull request may close this issue.
Motivation
At the moment, we only have one global timezone setting for the cms.
In some cases, we might have regions of different timezones in the same database.
Proposed Solution
request.region
is setAlternatives
Additional Context
This is a precondition of #663 and probably makes #662 obsolete.
The text was updated successfully, but these errors were encountered: