You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the DQL Frontend Plugin renders anything coming from the backend as-is. This is fine for most data, but for dates and timestamps, Backstage recommends to render them formatted for the locale of the user (ADR012).
To comply with ADR012, we'd need to know that the given column is a date or timestamp and use Luxon.toLocaleString to render it accordingly.
This also pulls in the necessity to deal with null values when not all entries contain a date or timestamp, something that's currently covered by the DQL query itself (no logic on the Frontend side).
Bad
2023-11-13T14:45:43.278000000Z
Good (for German/Austrian Locale)
13.11.2023 15:45:43
The text was updated successfully, but these errors were encountered:
Currently the DQL Frontend Plugin renders anything coming from the backend as-is. This is fine for most data, but for dates and timestamps, Backstage recommends to render them formatted for the locale of the user (ADR012).
To comply with ADR012, we'd need to know that the given column is a date or timestamp and use
Luxon.toLocaleString
to render it accordingly.This also pulls in the necessity to deal with
null
values when not all entries contain a date or timestamp, something that's currently covered by the DQL query itself (no logic on the Frontend side).Bad
2023-11-13T14:45:43.278000000Z
Good (for German/Austrian Locale)
13.11.2023 15:45:43
The text was updated successfully, but these errors were encountered: