Closed c-myers1 closed 1 year ago
Not explicitly. Can you give me a use case?
Standard CRUD. In building an admin panel around it all, you would want to see the list of resources (accounts, currencies, etc) and then edit, delete or add another.
The accountQuery request handles accounts, but yes the functionality is missing for other resources. It's really more CRUDL with L for list. I can see cases where you want to restrict access to "list" capability, which is one reason why accountQuery is a separate route. It makes sense to add this for other resources. I'll start work on that.
Thanks for pointing this out!
Code is in, hope to wrap documentation today and release.
Never say "hope to release today". Release 1.10.0 is out with a suite of query operations and improvements in existing queries. Updated documentation is available.
I didn’t notice any new stuff in the json api docs. E.g. which route returns all currencies?
Nuts. Updated the messages but not everything in the API. will fix. Generally {resource}/query will do the trick.
The navigation menu for the documentation was a manual process, and I missed updating that. Now it's automatic and all the new stuff is discoverable. There is still a problem with the codeselect JSON schema, but this has no operational impact.
I note you can only get a single item (resource) using the /get API routes. Is this deliberate?