1. Preferably you map the (reset) to a keybinding in your editor. 2. When I was still using boot, it had a watch filesystem task, and it was easy to run reset from there. 3. You could always e.g. add a ring middleware, so in dev-mode each new HTTP request refreshes your reloadable code

I've found that with bigger component systems (and access to current state in the repl), I don't actually like it reseting with every file save, so I use (1) - in emacs via .dir-locals.el

Actually, the problem I have with (reset) is that I use in-memory datomic db.

So every (reset) all the data is gone.

wrap-reload also does not seem to work..

ah, ok; well if it's just a question of defmutation, if you avoid caching your mutations/resolvers within a var (i.e. use defn or #'reference) and create new pathom parser with each request, that should work without (reset)

I am not able to make it work.

https://github.com/otwieracz/wires/tree/master/src/main/wires

Maybe you can see something inherently wrong?

The only way that is working is to enable wrap-reload and save file.

But I don't understand why I cant modify function at the runtime..

you want to be able to update a mutation’s body and eval it and have your system use that new version, correct?

But now it stopped working, too..

https://github.com/otwieracz/wires/blob/master/src/main/wires/mutations.clj#L23

if you re-eval the add-connector it's not going to be refreshed in the parser, because the var is cached

if that’s what you want, you can make a wrapper macro for defmutation, make it output a defn with a stable name and invoke that internal function in the mutation body

that’s what we’ve done in our project

@U09FEH8GN wouldn't it be enough to reference it via #'add-connector ?

but we (@U0CKQ19AQ and I) also strongly recommend test driven development on the server, rather than manual trial-and-error driven development

@pithyless i’m not sure what you mean

(def mutations [#'add-connector]) seems to break things

"class clojure.lang.ExceptionInfo: Mutation not found - {:mutation wires.mutations/add-connector}"

OK, seems like I've got it

https://github.com/otwieracz/wires/commit/bcdad99d3f3e3bfcfbe10dc0994fe11c87abede0

Thanks for your help!

(hope it will keep working :))

@slawek098 doesn't the reloaded workflow have any way to keep some state (your Datomic) across reloads?

you can indicate a ns isn’t to be reloaded

with tools-ns

I think you put metadata on the ns name?

or you could make a source dir that has your db in it, and the elide that dir from the call to set-refresh-dirs

There is http://clojure.github.io/tools.namespace/#clojure.tools.namespace.repl/disable-reload! - or just set the Metadata on the ns manually

I reload the defmutation namespace and the pathom parser namespace (I don’t need to reload the whole app). I use mount for state management and it automatically reloads the pathom state component when the file is recompiled.

we also have some authorization/permission stuff mixed in there

that NS is used by JVM and nodeJS envs

the JVM one has the internal function trick so you can re-eval a mutation definition and have it take affect immediately