0 Members and 1 Guest are viewing this topic.
Will start updating my backend to handle this later today, hope it won't break everything.. I used moment.js to parse the old date format, might just be a case of updating my parser function I guess.
Quote from: vikram on December 09, 2014, 08:33:43 pmQuote from: monsterer on December 09, 2014, 08:01:55 pmQuote from: abit on December 09, 2014, 06:07:38 pmFor example,with v0.4.24, "last_update": "20141208T051234"Now, "last_update": "2014-12-08T05:12:34"Woohoo! ISO correctness Yup. Per your original request: https://github.com/BitShares/bitshares/issues/857It isn't listed in the release change log, as well as other API changes.So it's better for (3rd-party) devs to subscribe the whole issue list?
Quote from: monsterer on December 09, 2014, 08:01:55 pmQuote from: abit on December 09, 2014, 06:07:38 pmFor example,with v0.4.24, "last_update": "20141208T051234"Now, "last_update": "2014-12-08T05:12:34"Woohoo! ISO correctness Yup. Per your original request: https://github.com/BitShares/bitshares/issues/857
Quote from: abit on December 09, 2014, 06:07:38 pmFor example,with v0.4.24, "last_update": "20141208T051234"Now, "last_update": "2014-12-08T05:12:34"Woohoo! ISO correctness
For example,with v0.4.24, "last_update": "20141208T051234"Now, "last_update": "2014-12-08T05:12:34"