This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-07-18
Channels
- # aleph (4)
- # beginners (70)
- # cider (66)
- # clara (16)
- # cljdoc (20)
- # cljs-dev (9)
- # cljsrn (2)
- # clojure (36)
- # clojure-ecuador (2)
- # clojure-italy (14)
- # clojure-japan (2)
- # clojure-nl (22)
- # clojure-uk (79)
- # clojurescript (133)
- # clojutre (2)
- # code-reviews (5)
- # cursive (5)
- # data-science (1)
- # datomic (47)
- # duct (2)
- # emacs (1)
- # figwheel-main (3)
- # fulcro (11)
- # funcool (1)
- # graphql (6)
- # hyperfiddle (4)
- # leiningen (4)
- # luminus (9)
- # lumo (8)
- # mount (4)
- # nrepl (2)
- # off-topic (19)
- # onyx (1)
- # re-frame (23)
- # reagent (91)
- # reitit (17)
- # ring-swagger (2)
- # shadow-cljs (43)
- # tools-deps (27)
- # vim (45)
@delaguardo r/routes
returns in future just the path + route data tuples, so the code is bit simpler. [metosin/reitit "0.1.4-SNAPSHOT"]
. Wrote a small guide on composing routers: https://metosin.github.io/reitit/advanced/composing_routers.html
thanks! will try it later today. So far Iām using your suggestion and all my tests are green.
how am i supposed to handle "conflicting" routes? eg both api/users/:id
and api/users/some-action
should work
@vale you can disable the conflict resolution, with {:conflicts nil}
router option. Conflicting route tree will use linear-router
, and the route ordering matters.
... or you could log the conflicts, see https://metosin.github.io/reitit/basics/route_conflicts.html