Type: New Feature
Affects Version/s: 3.20.0
Fix Version/s: 3.21.0
It can be challenging to implement our time zones conventions in areas of the Reference Application that do not enforce a separated client-server pattern over REST, such as in Java/Groovy Server Pages that are widespread over the Reference Application.
The idea is to control client-server time zones conversions through a centralised global property setting: "timezone.conversions" (for backward-compatibility.)
When existing and set to a truthy value this indicates that the time zones conversions should be enforced.
In the widespread case of GSPs it is much easier to convert server datetimes with Groovy in the view. However this requires the view
- To know whether the "timezone.conversions" is set to a truthy value.
- To know what the client time zone to convert to.
For the latter we decide to keep track of the client time zone through a user property named clientTimezone.