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
The current format "date":"2023:06:12-10:48:03", eg. of the /connect.php api does not follow RFC 3339 (https://www.rfc-editor.org/rfc/rfc3339#page-4). It rather seems completely arbitrary.
To be parsable by api consumers without additional efforts it should be:
2023-06-12T10:48:03
The text was updated successfully, but these errors were encountered:
It requires custom parsing instead of being able to use any standard like mentioned above. I was hoping- given its a custom format- that the api consumer is under control, too. If not happy to close. Year:Month:Day sure looks odd 😀.
The current format
"date":"2023:06:12-10:48:03"
, eg. of the/connect.php
api does not follow RFC 3339 (https://www.rfc-editor.org/rfc/rfc3339#page-4). It rather seems completely arbitrary.To be parsable by api consumers without additional efforts it should be:
The text was updated successfully, but these errors were encountered: