@wilkerlucio Any idea what it means when

[fulcro.client.impl.application] Mutation  fulcro.inspect.ui.transactions/add-tx  failed with exception Error: Assert failed: Path [:fulcro.inspect.ui.transactions/tx-list-id [:fulcro.inspect.core/app-id some-app.ui.root/Root] :fulcro.inspect.ui.transactions/tx-list] for append must target an app-state vector.
(vector? (get-in state data-path))

FYI: Anyone wanting to try out cljs 1.10 I’ve just pushed 2.3.1-SNAPSHOT to clojars. There were two minor changes needed for it to work. I’ve not done extensive testing, but I do a formal release as soon as I get some reports of larger applications working.

@wilkerlucio how do I access to top level AST from my outermost wrap-parser plugin?

I want a plugin that read top level AST, calculate a value from the AST and inject to env so the all reader plugins can access the value

@myguidingstar given this is the wrap-parser signature: (fn [parser] (fn [env tx])), the tx is your full query, so you can call query->ast on it to get the full source ast

I know, but I guess that's duplication

anything else to achieve the same goal?

not that I know, because the parser make this internally, currently it is kind wasterful, it calls query->ast on every recursive call, but for server processing thats usually not a problem

I see, so one more is no big deal 🙂

where is query->ast?

fulcro primitives

ok, I thought we've decoupled pathom from fulcro

not yet, but it might be in future

thank you very much

no problem