For example,
with v0.4.24, "last_update": "20141208T051234"
Now, "last_update": "2014-12-08T05:12:34"
Have to tweak my scripts..
EDIT:
The "blockchain_get_transaction" API changed as well.
Can confirm this ... already updated my scripts too .. not all of them though and not pushed the commits yet ...
Quote from: abit on December 09, 2014, 06:07:38 PM
For example,
with v0.4.24, "last_update": "20141208T051234"
Now, "last_update": "2014-12-08T05:12:34"
Woohoo! ISO correctness :)
Quote from: monsterer on December 09, 2014, 08:01:55 PM
Quote from: abit on December 09, 2014, 06:07:38 PM
For 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: vikram on December 09, 2014, 08:33:43 PM
Quote from: monsterer on December 09, 2014, 08:01:55 PM
Quote from: abit on December 09, 2014, 06:07:38 PM
For 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
It 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: abit on December 10, 2014, 01:16:33 AM
Quote from: vikram on December 09, 2014, 08:33:43 PM
Quote from: monsterer on December 09, 2014, 08:01:55 PM
Quote from: abit on December 09, 2014, 06:07:38 PM
For 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
It 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?
I've added it to the changelog.
It is difficult to keep track of every change; we try to collect the most important ones for the changelogs. But we are not API stable yet and still may break the API at any time.
Thanks for your hard work
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: svk on December 10, 2014, 09:10:32 AM
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.
Good luck :)
Quote from: svk on December 10, 2014, 09:10:32 AM
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.
What I did was to check the length of the string, if it was too short to be ISO standard, I parse it manually, as you have - if not, send it to the regular system date parser. That way you handle both cases :)