bark: Give wallet developers the tooling to add metadata to movements
This adds some tooling to add metadata to movements. The key design decisions
- Use RFC 7396 in the API. Coming up with how to merge json objects can be tricky. I just picked a standard.
- I tested as much as possible in unit tests
- I moved
GET /api/v1/wallet/historyto/api/v1/history. I am open to change this back if we have strong arguments
- check or remove this line after you've added a CHANGELOG entry or if your PR doesn't need one (they should go into
CHANGELOG/unreleased/)
Edited by Erik De Smedt