Files
notifications-api/app
Katie Smith 4ffdd32054 Keep the marshmallow v2 way of serializing DateTimes
Marshmallow v3 has changed the way that DateTimes get serialized
(https://marshmallow.readthedocs.io/en/stable/upgrading.html#datetime-leaves-timezone-information-untouched-during-serialization).

In order to avoid breaking anything, we want to keep the existing way of
handling DateTimes for now - this could be changed later. We can't just
pass a `format` argument to a DateTime field with the old format, which
looked like this `2017-09-19T00:00:00+00:00`. When we tried that,
Marshmallow then expected data that we are loading to also have that
format, which it doesn't.

This adds a new field, which serializes data in the old format but which
doesn't require data that is being deserialized to have such a precise
format.
2022-05-25 11:35:44 +01:00
..
2021-03-15 17:18:20 +00:00
2022-04-29 12:28:08 +01:00
2022-05-25 11:35:44 +01:00
2022-05-25 11:35:44 +01:00
2022-05-25 11:35:44 +01:00
2022-05-25 11:35:44 +01:00
2022-05-25 11:35:44 +01:00
2022-05-25 11:35:44 +01:00
2022-05-25 11:35:44 +01:00
2021-05-12 17:48:38 +01:00
2022-04-29 12:28:08 +01:00
2022-05-03 14:42:59 +01:00
2021-03-12 11:45:45 +00:00
2021-03-12 11:45:45 +00:00
2022-05-03 14:42:59 +01:00