Added last_updated to /v2/latest

[whitehat007]

Also added source info field

[ExpDev07]

This doesn’t really give the last updates, it’ll just say whatever time is the endpoint is accessed. Also, to comply with the JSON-API spec, should perhaps this information be put under a “meta” key?

[whitehat007]

Is it possible to get the time of the last update? If so I think that would be preferable.

We could put it under a meta key, but I feel like that's rather unnecessary for just 1-2 keys--plus, that doesn't conform to the v1 API. Either way works, but I just think it should be consistent (and backward-compatible so it doesn't break workflows).

[ExpDev07]

The point of the /v2/ was to introduce major changes. We just have to stay compatible with the current v2 endpoints and not v1 (they are now undocumented but staying for legacy support and not to break apps).

And yes, it’s possible. You can go into the timeline.py, and add a computed field which just grabs the latest key in the timelines property dict (see latest). Then you just gotta make sure to add it to the serialization method dict.

[ExpDev07]

Oops, I meant timeline.py, not location. The last_update would technically be apart of the timelines.

However, I agree that it would be better having it attached to the actual location object, in which case we can just store the time when the data was last retrieved from JHU. Either way works, but which one is the best, idk.

[whitehat007]

Alright, then adding the meta key is the way to go.

I looked at the return data from the timelines property, but the timestamp is always at midnight GMT, which isn't really useful. However, the Last update field here shows the latest update by country, which would be very useful (and can be attached to the location object). For the case of /v2/latest, we could just take the most recent date/time from that field and use that.

[ExpDev07]

Yup, it’s always midnight. JHU updates their data only once a day anyways.

[Kilo59]

Will be adding a similar feature, hopefully soon.