This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-01-06
Channels
- # aleph (13)
- # announcements (1)
- # babashka (89)
- # beginners (23)
- # calva (14)
- # circleci (7)
- # clj-kondo (39)
- # clj-on-windows (1)
- # cljdoc (5)
- # cljsrn (29)
- # clojure (98)
- # clojure-art (3)
- # clojure-conj (5)
- # clojure-europe (14)
- # clojure-nl (1)
- # clojure-norway (9)
- # clojurescript (18)
- # clr (39)
- # code-art (3)
- # community-development (3)
- # cursive (3)
- # emacs (11)
- # events (1)
- # fulcro (12)
- # graalvm-mobile (16)
- # graphql (3)
- # gratitude (1)
- # honeysql (19)
- # java (7)
- # joyride (23)
- # lsp (22)
- # malli (2)
- # missionary (25)
- # off-topic (15)
- # polylith (15)
- # rdf (5)
- # reagent (9)
- # reitit (3)
- # scittle (3)
- # shadow-cljs (37)
- # slack-help (2)
- # sql (10)
I am confused by the documentation of reitit.frontend, and I'm not sure how I can actually restrict routes because IDK how it compares to reitit on the backend. I need to restrict certain pages if an atom doesn't have a specific value in it. But I also need to be able to pass params from the URL to the components I'm rendering. This is the closest I got.
wrap-restricted
takes someone to login if they aren't logged in. But this solution doesn't really work for me. Is there a more idiomatic way to do this?
I can use muuntaja decode/encode the request/response body to/from kebab case/camelCase, but is there a similar facility to kebabify query parameters in a GET request? i.e., if I do GET /foo?lastName=bar
, and if I have a malli spec like {:parameters {:query [:map [:last-name :string]]}}
, it would appear in {:parameters {:query {:last-name "bar"}}}
. So far it appears the only way to do this is to use a bit of middleware to update the {:parameters {:query...}}
structure directly.