I'm pretty new to the clojure repl workflow / reitit

Hey! Here is an simple example of a reitit friendly setup https://gist.github.com/athomasoriginal/15ab9f5e01832fda677f80dd635aff46. Let me know if this helps 🙂

I think the #'app in the run-jetty call might be where I'm going wrong

In my integrant component that creates my handler, I am returning the result of a function called make-app that itself just calls ring/ring-handler . So, I am returning a function that is effectively a closure of all my ring/routes config I guess.

I think I'm doing virtually the same as this example https://github.com/metosin/reitit/blob/master/examples/ring-integrant/src/example/server.clj

That example would also require me to ig-repl/reset if anything changed in the handler setup (edit: or at least I think it would, I've not tried to run it)

> I think the #’app in the run-jetty call might be where I’m going wrong Yes, the #'app bit is key.

I think the integrant example you linked is a bit overkill.

What I would say is try the gist I provided and the only thing that needs to become a part of your integrant system is the (def server (jetty/run-jetty #'app {:port 3000 :join? false}))) call. From there, your routes should be reloadable.

Integrant tip: avoid breaking up your system too much, too early.

I have my handler integrant "component" dependent on my database component as I need (or I think I need) to inject that into my handler component so I can provide it to requests via middleware

This is why I say avoid breaking up the system too early 😉: Makes it harder to see some of the options:

(defn wrap-handler 
  [handler options-map]
  (fn [req] 
    (handler (assoc req :options options-map)))))

(def server 
  (jetty/run-jetty 
    (wrap-handler #'app {:db your-db-conn-here})
    {:port 3000 :join? false})))

With the above, you can now pass options-map anywhere you want…and not just the routes, but whoever else needs them.

what you're saying does make sense

I'll give removing that db dependency a try and see if I can't wrap a handler ref with it instead. Thanks