On Wed, Jun 18, 2014 at 11:05 AM, Fredo Erxleben fredo.erxleben@tu-dresden.de wrote:
On 17.06.2014 21:17, Jeroen De Dauw wrote:
Hey,
Sorry for the passive-agressive tune, but having to write a ner Json
(de)serialization every quarter year is not that productive.
Considering we have not changed the internal format like this before, and that we are changing it to the one already used by the web API, in part to have less differences, this seems to be an unfair characterization to me.
Okay, strike the "quarter". The point is, that there have been a bunch of changes and they all have to be supported. I am aware that there will be probably no perfect Json version. While looking at the dumps it seems, that, when updated, items are written out as the then actual Json version. Items not updated for a long time therefor remain in an older Json.
TLDR:
- having a versioning tag would help a lot
- not mixing Json versions in the dump would help a lot
We are working on that right now.
- documenting the existing versions would help a lot (code is no
documentation)
Even if no-one wants to do it retroactively, it would be nice if we could make a habit out of it in the future. </whining><working>
Cheers Lydia