expanded export and datetime attrributes#16447
Merged
brandonkelly merged 4 commits into5.6from Jan 20, 2025
Merged
Conversation
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.
Description
Since
5.3.0-beta.1when runningtoArray()on a model, the datetime attributes (e.g.dateCreated,dateUpdated) will always show in UTC. Previously, they were using the app’s timezone (Settings > General Settings).This led to a change in behaviour where expanded export of elements started including the datetime attributes in UTC.
This PR ensures that the datetime attributes are returned in the app’s timezone again.
Related issues
n/a; outcome of a chat with Oli