In the Evaluator, we add Z to the end of the date time from Drupal because the stored value in Drupal is always UTC but does not validate as a date-time per RFC3339
The issue is the frontend code turns the entered value back into a value that does validate for RFC3339 and then we end up adding the Z when a time-offset already exists
In
📌
Implement saving block settings forms
Active
we added a temporary workaround to make sure we only add the Z if the time offset isn't already there.
This issue is to explore if there's a more robust approach.
Active
0.0
Data model
Let's wait to do this until after 📌 Move clientside assumptions about prop form data shape into a series of prop specific transforms Active lands.
📌 Move clientside assumptions about prop form data shape into a series of prop specific transforms Active is in.
(And just noticed while reviewing #3493941 that it appeared there too.)