A new version of the Amatino API is live in all regions. API 0.0.8 may be substantially backward compatible with 0.0.7, however, is not tested as such and relying on backwards compatibility during these 0.0.X releases is not recommended.
- Fixed a bug which could cause a stale, cached Performance or Position to be returned after a Transaction insertion
- Fixed a bug causing Custom Unit update requests to fail, returning a 500 code.
- Account objects now feature a ‘Children’ parameter, which contains integer IDs of all direct child Accounts.
- Fixed a rare condition wherein internal telemetry recording could fail due to a unique key constraint violation, causing the API to spew 500 errors in response to any request
- Substantial code-style enhancements in the core API to ease maintainability
- Improved test coverage over rare edge cases in Account operations
A tiny update has been released for Amatino’s Node library. 0.0.14 fixes a silly bug in the inbuilt Node version enforcement script. The script is run after installation, and was supposed to stop Node versions lower than 10.4 from running Amatino JS. Instead it was stopping versions greater than 11.0 from running it!
Amatino JS 0.0.14 is available on NPM and on GitHub.
A new version of the Amatino API has been deployed to all regions. 0.0.7 fixes a single bug, wherein the Account update requests yielded a bunch of gibberish rather than the updated Account object.
This morning I realised, to my substantial embarrassment, that Trees were missing from the Amatino API HTTP documentation.
Trees are, in my humble opinion, the most exciting object the Amatino API can build. They are hierarchical structures of every Account in an Entity, including balances, recursive balances. They are a great way to get a whole-Entity picture.
Somehow, I had ommitted them from the docs. That omission is now fixed! In future, I will need to do some work to flesh out the related Tree Node documentation. It is not yet clear how the Tree Node behaves when it omits data due to a lack of read permissions on a particular Account.
The Amatino API HTTP documentation has been updated. This update corrects errors in references to Global Units and Custom Units. Previously, the documentation stated that such units should be identified by their string codes. For example,
'usd' for U.S. Dollars.
Now, the documentation states that units should be identified by their integer identifiers. For example,
5 for U.S. Dollars.
This error was the result of some earlier experiments with removing integer unit identifiers in favour of string identifiers. The experiments did not go well, and lots of problems resulted. So, I reverted to integer identifiers, but forgot to update the documentation.