Hello friends, does someone already had this kind of error Unknown app state mutation. Have you required the file with your mutations? - and yes, my defmutation is on the same namespace as the defsc where it’s called

typo? maybe bad quoting?

nope - defmutation does fully qualified namespad symbol right ?

can you share the code for the mutation and the call site?

yep, let me make a gist

https://gist.github.com/dupuchba/3342f587e3c5881e0411dd0b31b5aae4

defmutation edit-form-number vs (prim/transact! this [(edit-phone-number, there is a typo form vs phone

no way

shame on me

really sorry

no worries

thats why I love using cursive, it can auto-complete on those, and complain if they are wrong 🙂

indeed, cursive is excellent

but I felt in love with emacs - I can’t change that

offtopic: i think there are emacs linters which can check those kind of errors

https://twitter.com/borkdude/status/1047135083998732288

when creating parser for pathom, how can I remove keys with value :com.wsscode.pathom.core/not-found? e.g., {:a 1 :b :com.wssscode.pathom.core/not-found} becomes just {:a 1}

@mavbozo yes, there’s a plugin…

trying to remember the name

elide-not-found, I think

with post-process-parser-plugin?

@mavbozo Tony said the right things, here you can findf the post process: https://github.com/wilkerlucio/pathom/blob/master/src/com/wsscode/pathom/core.cljc#L657-L663

and elide not found: https://github.com/wilkerlucio/pathom/blob/master/src/com/wsscode/pathom/core.cljc#L222-L225

you can use as: ::p/plugins [(p/post-process-parser-plugin p/elide-not-found)]

Released 2.6.6 to clojars. This fixes the mysterious rendering bug in 2.6.5, which was due to accidental name shadowing.

just tested with 2.6.6, refresh issues are gone 🙂