@pontus.colliander The built-in parser on the client is written to use db->tree for you.

There is nothing manual about it. You can use initial state to build an initial co-located state tree (which is auto-normalized on startup), and the queries are processed by the internal parser for you. Loading is a separate mechanism. So basically you can plug in an alternate network component/layer if you want, but other than that there is not much to write to make things work.

I see, thanks @tony.kay @claudiu

Hm I am trying to write a spec with generator for fulcro id/tempid and I'm failing: (s/def :db/id (s/or :tempid (s/with-gen prim/tempid? (gen/fmap tempid/->TempId (gen/uuid))) :id (s/and integer? pos?)))

where s is spec.alpha, gen is spec.gen.alpha

After running (gen/sample (s/gen :db/id)) I get ClassCastException clojure.test.check.generators.Generator cannot be cast to clojure.lang.IFn clojure.spec.alpha/spec-impl/reify--1987 (alpha.clj:888) which is weird, as I cannot see how there is anything wrong.

@roklenarcic the generator needs to be a function of zero arguments that returns the generator, looks like you are returning the generator directly

this might work: (s/def :db/id (s/or :tempid (s/with-gen prim/tempid? #(gen/fmap tempid/->TempId (gen/uuid))) :id (s/and integer? pos?)))

and extra tip: you can replace (s/and integer? pos?) with pos-int?

@wilkerlucio works now, thanks

it can be a bit confusing

when the arg is a generator and when a generator constructing fn

for spec, AFAIK it's always a constructing fn, directly generators are used on more inside levels (like when composing generators)

but it's easy to mess up, and over time we tend to remember better when to use what 🙂