This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-10-16
Channels
- # 100-days-of-code (1)
- # announcements (1)
- # beginners (93)
- # boot (46)
- # cider (40)
- # cljdoc (4)
- # cljs-dev (7)
- # clojure (78)
- # clojure-conj (12)
- # clojure-dev (17)
- # clojure-italy (5)
- # clojure-nl (10)
- # clojure-spec (34)
- # clojure-uk (36)
- # clojurescript (56)
- # code-reviews (6)
- # core-async (31)
- # cursive (12)
- # datascript (9)
- # datomic (19)
- # devops (2)
- # editors (3)
- # emacs (6)
- # events (2)
- # figwheel (1)
- # figwheel-main (11)
- # fulcro (59)
- # graphql (10)
- # hyperfiddle (3)
- # keechma (5)
- # leiningen (26)
- # luminus (1)
- # nrepl (5)
- # re-frame (5)
- # reitit (10)
- # shadow-cljs (64)
- # spacemacs (29)
- # tools-deps (6)
- # uncomplicate (8)
- # vim (2)
- # yada (4)
`(def routes (rf/router [["/" {:name ::home :view home-page/root-ui}] ["/about" {:name ::about :view about-page/root-ui}] ["/login" {:name ::login :view login-page/root-ui}] ["/item/:id" {:name ::item :view item-page :parameters {:path {:id s/Int} :query {(s/optional-key :foo) s/Keyword}}}]] {:data {:coercion rsc/coercion}}))`
@ikitommi was parameter validation changed to allow the param route data hashmap keys to be strings?
@alex340 By looking at the code (https://github.com/metosin/reitit/blob/master/modules/reitit-spec/src/reitit/coercion/spec.cljc#L120-L135), it seems that the response coercion is called the same way as request coercion.
oh, true that that it doesn’t call the st/encode
, but same as the request coercion doesn’t call st/decode
- but the code is effectively the same, just inlined.
@thiru0130 looks correct, maybe something wrong with the login-page/root-ui
?