you have to remember to also reload the file that builds up the env, so you can rebuild your indexes with the new resolver configuration

I think the problem is that the resolvers are in def , so I have to reload the namespace and the namespace that call that name space, I did it and it worked, thank you

we can use the #'my-resolver trick when building the index right @U066U8JQJ?

that is not enough, the problem is that what matters for pathom is the indexes, which get created on the pci/register call, this is why this needs to be re-evaluated when resolver changes to compute the new indexes

there are possible tricks around, like keeping the indexes in an atom and derrefing at run time (using plugins), this approach has an issue with removing things, another approach would be to keep the resolvers in some mutable atom, and on each call re-compute all of it (something you surely don't wanna do in prod, but is useful in dev time)

what we do is to create pathom-env as fn, and during testing/dev we create always a new one on each call. ex:

(defn query! [context tx]
  (interface/query! (p.eql/boundary-interface   (interface/pathom-env context)) txl))

similar for dev, we have an interceptor that creates the pathom boudnary-interface for each request

nice

still the downside is that pathom-viz connector doesn’t see the changes, so when needed we connect to connector via http that triggers the reload interceptor.

Here what I mean, I think it’s a bug actually https://gist.github.com/cyppan/bbdfdb16d267051ad1e675c4a38ced5f

that optional is misplaced, it should be [{(pco/? :nested) [:id :name]}]

oh yes I messed up my repro case sorry I’ve updated the gist, I still have the problem https://gist.github.com/cyppan/bbdfdb16d267051ad1e675c4a38ced5f

confirmed the report, tracking issue: https://github.com/wilkerlucio/pathom3/issues/107

ok thanks