The vase.api/schemas value is inconsistent. The first 2 instances show:
:vase.api/schemas [:account/item]
but after that it changes to:
:vase.api/schemas [:accounts/user]
The schema description is confusing. It starts with a cookbook process saying "Start by clearing out the current value of :vase/norms and replace it with this:
:vase/norms
{:your-first-api/accounts {}
}
But after that ":your-first-api/accounts" is replaced with 2 schemas: :accounts/item and :accounts/user, and there is no schema ending in /accounts. That makes for confusion in trying to reconcile the initial edit instructions with the followup snippets. It would be really helpful to have an "end result" edn example available.
This is probably obvious and planned, but it wold be help to have curl examples at each stage, esp. POST examples - since it's not obvious that you need to use "payload" (as mentioned in a recent issue report).
Thanks, this is great stuff! I'm enjoying learning vase. Hope this is helpful. Wasn't sure if you'd prefer pull requests or issue reports for these doc changes.
Description
Documentation for creating your first API in https://github.com/cognitect-labs/vase/blob/master/docs/your_first_api.md needs some edits
:vase.api/schemas [:account/item]
but after that it changes to:
:vase.api/schemas [:accounts/user]
But after that ":your-first-api/accounts" is replaced with 2 schemas: :accounts/item and :accounts/user, and there is no schema ending in /accounts. That makes for confusion in trying to reconcile the initial edit instructions with the followup snippets. It would be really helpful to have an "end result" edn example available.
Thanks, this is great stuff! I'm enjoying learning vase. Hope this is helpful. Wasn't sure if you'd prefer pull requests or issue reports for these doc changes.