v0.13.0

Breaking changes

• What you write is called a request, not a query. In JMAP, Foo/query is the method that searches, and a file holding methodCalls is a Request object as RFC 8620 defines it, so calling that file a query collided with the specification's own word. -queries is now -requests, the jmapc.json key "queries" is "requests", and the defaults are requests for the input and client for the output, in place of queries and jmapq. A project keeping its old layout passes the paths it already uses; one on the defaults renames the two directories and regenerates. The generated code itself is unchanged apart from its package name. (#70)

Documentation

• The README says what jmapc does before why it exists, opening with a request and the call generated from it, then a list of five features. The reference moved to docs/, a file to a subject: writing a request, verification, the command, the runtime, push, paging, testing, the Rust and TypeScript clients, vendor extensions, coverage, and working on jmapc. A new section says how jmapc differs from the JMAP client libraries — the request written in JMAP rather than in an API of the library's own, the checking done before the program runs, and the response typed to what the request asked for. Both languages are split the same way. (#68)