Use ISO UTC for match dates in DCAR data models in frontend #28572
Description
It seems that the Java ZonedDateTime that's used for the match date field in PA Client is giving the following date formats for matches:
- 2026-06-13T20:00+01:00[Europe/London] when the match is in british summer time
- 2025-10-26T14:00Z[Europe/London] when the match is in greenwich mean time
In javascript it doesn't yet understand the [Europe/London] part of the date time. Although, the RFC 9557 format in Temporal.ZonedDateTime has been introduced but doesn't yet have support in all browsers.
So for now we need to remove the zone part from the date string. You can see how the Date behaves in node with the above examples:
It'll be ideal to fix this on frontend side, and return a ISO 8601 in UTC for match dates at the stage where the json body is generated for DCAR.
More details on this comment