(process env tx)
(process env entity tx)
Evaluate EQL expression using async runner.
This interface allows you to request a specific data shape to Pathom and get the response as a map with all data combined.
This is efficient for large queries, given Pathom can make a plan considering the whole request at once (different from Smart Map, which always plans for one attribute at a time).
At minimum you need to build an index to use this.
(p.eql/process (pci/register some-resolvers)
[:eql :request])
By default, processing will start with a blank entity tree. You can override this by sending an entity tree as the second argument in the 3-arity version of this fn:
(p.eql/process (pci/register some-resolvers)
{:eql "initial data"}
[:eql :request])
For more options around processing check the docs on the connect runner.
Evaluate EQL expression using async runner. This interface allows you to request a specific data shape to Pathom and get the response as a map with all data combined. This is efficient for large queries, given Pathom can make a plan considering the whole request at once (different from Smart Map, which always plans for one attribute at a time). At minimum you need to build an index to use this. (p.eql/process (pci/register some-resolvers) [:eql :request]) By default, processing will start with a blank entity tree. You can override this by sending an entity tree as the second argument in the 3-arity version of this fn: (p.eql/process (pci/register some-resolvers) {:eql "initial data"} [:eql :request]) For more options around processing check the docs on the connect runner.
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close