All notable changes to this project will be documented in this file. This change log follows the conventions of keepachangelog.com.
_typename
metafield support{:venia/queries [[:employee [[:name {:preferNickname true}] :address]]]}
Breaking changes:
Moved away from huge nested vectors as query definitions to neat query map definitions. After all, simplicity is all that matters. Now, queries are defined like this:
{:venia/operation {:operation/type :query
:operation/name "employeeQuery"}
:venia/variables [{:variable/name "id"
:variable/type :Int}
{:variable/name "name"
:variable/type :String}]
:venia/queries [{:query/data [:employee {:id :$id
:active true
:name :$name}
:fragment/comparisonFields]
:query/alias :workhorse}
{:query/data [:employee {:id :$id
:active false}
:fragment/comparisonFields]
:query/alias :boss}]
:venia/fragments [{:fragment/name "comparisonFields"
:fragment/type :Worker
:fragment/fields [:name :address [:friends [:name :email]]]}]}
:venia/queries
is only one required key, others are optional. However, rest of data needs to be valid as well if added.
Query's data can be also defined as simple vector:
{:venia/queries [[:employee {:id 1 :active true} [:name :address [:friends {:id 1} [:name :email]]]]]}
Notice how fragments are defined and referenced in code example above.
Initial release
Can you improve this documentation?Edit on GitHub
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close