This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-05-20
Channels
- # announcements (27)
- # aws (1)
- # beginners (62)
- # boot (5)
- # calva (56)
- # clj-kondo (6)
- # cljdoc (3)
- # cljsrn (4)
- # clojure (65)
- # clojure-dev (17)
- # clojure-europe (2)
- # clojure-italy (17)
- # clojure-nl (24)
- # clojure-spec (30)
- # clojure-uk (14)
- # clojurescript (35)
- # clr (7)
- # cursive (8)
- # data-science (3)
- # datascript (38)
- # datomic (15)
- # emacs (16)
- # fulcro (34)
- # hyperfiddle (1)
- # immutant (1)
- # luminus (7)
- # nrepl (1)
- # off-topic (38)
- # pedestal (2)
- # planck (10)
- # re-frame (7)
- # reagent (7)
- # reitit (9)
- # shadow-cljs (36)
- # sql (19)
- # tools-deps (11)
- # vim (64)
- # xtdb (18)
@levitanong The bracket-syntax might help on the colon-tjing, but there is no way currently to force a certain path-parameter syntax for a router. So, both colon & bracket syntaxes are enabled by default.
about encoding of path params, no option for that either. Please write issues if you need those.
@ikitommi I will write an issue, thanks! Also, how would bracket syntax help with the colon thing?
["/olipa/ker:kikka/{avaruus}"]
should work and bind just :avaruus
as a path param. Doesn't help if the colon is supposed to be right after /
, then it's interpreted as a path-param.
Should be easy to add option to explicitly define which syntax(es) are supported for a router.
got it!
So stupid question. I am using re-frame with reitit fe. I have a event that deals with page navigation. Essentially it calls push-state
(https://github.com/metosin/reitit/blob/057fae9e4602a6f5a48a99b0ded694ffe40378ca/modules/reitit-frontend/src/reitit/frontend/easy.cljs#L38)