Author Topic: Time format changed in v0.4.25-RC1 RPC API?  (Read 2758 times)

0 Members and 1 Guest are viewing this topic.

Offline monsterer

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 :)
My opinions do not represent those of metaexchange unless explicitly stated.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore

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 :)

BitShares committee member: abit
BitShares witness: in.abit

Offline svk

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.
Worker: dev.bitsharesblocks

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
BitShares committee member: abit
BitShares witness: in.abit

Offline vikram


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.

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore

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?
BitShares committee member: abit
BitShares witness: in.abit

Offline vikram

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

Offline monsterer

For example,
with v0.4.24, "last_update": "20141208T051234"
Now, "last_update": "2014-12-08T05:12:34"

Woohoo! ISO correctness :)
My opinions do not represent those of metaexchange unless explicitly stated.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Can confirm this ... already updated my scripts too .. not all of them though and not pushed the commits yet ...

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
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.
« Last Edit: December 09, 2014, 06:27:59 pm by abit »
BitShares committee member: abit
BitShares witness: in.abit