Skip to content
New issue

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

Use default type cast for recorded_at #271

Merged
merged 1 commit into from
Feb 27, 2024

Conversation

tagliala
Copy link
Member

Previously, recorded_at was consistently returned in UTC format, with the reason for this decision not explicitly documented in the commit history.

This commit modifies the behavior to use the application's configured timezone for recorded_at, aligning with the default type cast for timestamp fields.

This adjustment ensures that timestamp data is presented in a more intuitive format for users, potentially enhancing user experience and data interpretation.

Before:

Activity.last.history.first.recorded_at
=> 2024-01-05 14:40:18.656918 UTC

After:

Activity.last.history.first.recorded_at
=> Fri, 05 Jan 2024 15:40:18.656918000 CET +01:00

Previously, `recorded_at` was consistently returned in UTC format, with
the reason for this decision not explicitly documented in the commit
history.

This commit modifies the behavior to use the application's configured
timezone for `recorded_at`, aligning with the default type cast for
timestamp fields.

This adjustment ensures that timestamp data is presented in a more
intuitive format for users, potentially enhancing user experience and
data interpretation.

### Before:

```
Activity.last.history.first.recorded_at
=> 2024-01-05 14:40:18.656918 UTC
```

### After:

```
Activity.last.history.first.recorded_at
=> Fri, 05 Jan 2024 15:40:18.656918000 CET +01:00
```
@tagliala tagliala merged commit ee5c45f into master Feb 27, 2024
13 of 14 checks passed
@tagliala tagliala deleted the chore/do-not-convert-recorded-at branch February 27, 2024 08:57
tagliala added a commit that referenced this pull request Feb 27, 2024
This method was used in features that were removed (#268 and #271) and
the reason for converting ts values selected from the timeline query
is not explicitly documented in the commit history and appears to
be redundant (they are already timestamps)
tagliala added a commit that referenced this pull request Feb 27, 2024
This method was used in features that were removed (#268 and #271) and
the reason for converting ts values selected from the timeline query
is not explicitly documented in the commit history and appears to
be redundant (they are already timestamps)

After conducting manual tests on the `usec`s, it was determined that
the issue reported in issue #32 is no longer valid.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant