Q: Why disallow queries which address multiple routes?

[acron0]

Firstly, great library! I'm looking for some guidance on how best to approach this problem, which boils down to the way the graph is structured, I suspect.

(def graph
  {(with :functions/list get-functions)
   [:function/name
    :function/id
    :function/version]
   (with :workspaces/list-by-owner get-workspaces-by-owner)
   [:workspace/name
    :workspace/id]})

I'm fielding queries that look like this:

(dispatch graph '{(:workspaces/list-by-owner "Bob") [:workspace/name :workspace/id]
                  :functions/list [:function/name :function/id]})

So naturally, this is falling foul of the 'one root per query' constraint, and my first inclination is to challenge that constraint, unless there is a better way to build my graph which facilitates this kind of query. Any advice appreciated, thanks!

[karlmikko]

try

'[{(:workspaces/list-by-owner "Bob") [:workspace/name :workspace/id]}
  {:functions/list [:function/name :function/id]}]

[acron0]

Spoke too soon ...
ExceptionInfo Value does not match schema: (not (map? a-clojure.lang.LazySeq))