This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-20
Channels
- # aleph (12)
- # announcements (7)
- # aws (6)
- # babashka (36)
- # beginners (161)
- # boot (1)
- # calva (6)
- # cider (21)
- # clj-kondo (13)
- # cljs-dev (28)
- # cljsrn (1)
- # clojars (3)
- # clojure (13)
- # clojure-colombia (1)
- # clojure-europe (10)
- # clojure-spec (12)
- # clojure-uk (47)
- # clojuredesign-podcast (2)
- # clojurescript (67)
- # datascript (8)
- # datomic (21)
- # duct (3)
- # emacs (6)
- # events (1)
- # fulcro (6)
- # graalvm (98)
- # jobs (1)
- # kaocha (18)
- # luminus (1)
- # malli (7)
- # off-topic (56)
- # pathom (5)
- # re-frame (18)
- # reagent (3)
- # reitit (9)
- # remote-jobs (3)
- # rewrite-clj (10)
- # ring (1)
- # shadow-cljs (155)
- # spacemacs (2)
- # sql (5)
- # tools-deps (27)
- # vim (86)
- # xtdb (2)
Hi! I am trying to move to reitit and am having trouble: “Router contains conflicting route paths”. Currently I have the following routes: “users” “users/active” “users/archived” “users/:id” “users/:id/settings” How can I handle this case with reitit?
yes, but if you also add a wildcard (:id) you will get a canflict
@ikitommi thanks, didn’t know about it
But is there some way to get the similar result without using {:conflicts nil}
?
Let’s say we have
[/users/:filter]
[/users/:id]
where :filter is always a string, and :id is always a number.@zelark no, there is no selection of routes based on parameter types. If you disable the conflict resolution, the conflicting routes are matched in order and the first match wins.
thanks again