Description
The purpose of this topic is to ask for clarification on a date format inconsistency on the /v3/build/:buildId endpoint.
Example:
{
...
"started_at":"2019-10-03T14:53:57Z",
"finished_at":"2019-10-03T14:54:55Z",
...
"commit":{
...
"committed_at":"2019-10-03T14:53:00Z"
},
...
"updated_at":"2019-10-03T14:54:55.687Z"
}
As it can be seen the updated_at
value has a date format that includes milliseconds, while all other dates do not. This may present some troubles for some JSON parsers.
The question is: is this behavior intended?