This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-04-26
Channels
- # aleph (5)
- # announcements (9)
- # beginners (115)
- # boot (36)
- # calva (13)
- # cider (4)
- # clara (7)
- # cljs-dev (27)
- # cljsrn (20)
- # clojure (182)
- # clojure-conj (3)
- # clojure-dev (4)
- # clojure-europe (3)
- # clojure-italy (2)
- # clojure-nl (4)
- # clojure-uk (34)
- # clojurebridge (3)
- # clojurescript (19)
- # clojureverse-ops (3)
- # core-typed (1)
- # cursive (12)
- # data-science (3)
- # datomic (16)
- # emacs (9)
- # events (5)
- # figwheel-main (11)
- # fulcro (14)
- # graphql (7)
- # jobs (10)
- # jobs-discuss (6)
- # lein-figwheel (8)
- # leiningen (2)
- # lumo (22)
- # mount (1)
- # nrepl (7)
- # off-topic (69)
- # overtone (17)
- # pathom (3)
- # quil (1)
- # re-frame (5)
- # reagent (23)
- # reitit (6)
- # remote-jobs (1)
- # rewrite-clj (4)
- # ring (38)
- # shadow-cljs (54)
- # sql (9)
- # uncomplicate (5)
- # xtdb (1)
i want to do reverse routing inside a ring handler, but in my handler function the router is (necessarily) not yet defined because the routes haven't been compiled yet.
this example: https://metosin.github.io/reitit/ring/reverse_routing.html shows the problem, the router
in there has not been defined. I've tried using declare
to resolve this mutual dependency but it breaks my use of mount
. What's a good pattern for this?
@conan The router is injected into the request and (:reitit.ring/router request)
should summon it out.
i'm a little stuck on coercion using reitit.coercion.spec
.
using schema works fine:
{:name :view/home
:coercion reitit.coercion.schema/coercion
:parameters {:path {:id s/Uuid}}}
how might i go about using spec instead to do the same? i checked in the tests but they all seem to be schema based 🙂