This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-01-17
Channels
- # announcements (1)
- # babashka (26)
- # beginners (28)
- # biff (8)
- # calva (45)
- # cider (62)
- # clara (3)
- # clj-kondo (34)
- # cljfx (1)
- # clojure (72)
- # clojure-belgium (1)
- # clojure-canada (13)
- # clojure-conj (2)
- # clojure-dev (3)
- # clojure-europe (19)
- # clojure-nl (1)
- # clojure-norway (1)
- # clojure-uk (8)
- # clojurescript (10)
- # clr (36)
- # core-logic (13)
- # cursive (2)
- # datalevin (2)
- # datomic (23)
- # fulcro (13)
- # graphql (23)
- # instaparse (1)
- # introduce-yourself (4)
- # jobs (1)
- # jobs-discuss (13)
- # lsp (30)
- # luminus (7)
- # malli (2)
- # off-topic (57)
- # polylith (13)
- # portal (5)
- # reagent (32)
- # reitit (6)
- # remote-jobs (1)
- # shadow-cljs (25)
- # xtdb (12)
heya! Is there a malli equivalent of https://github.com/metosin/reitit/blob/master/doc/basics/route_data_validation.md
not yet, but one of the motivations for building malli was the frustration how complex the closed-map-spec validation got in Route data validation.
cool, thanks for the quick answer!!
great question, and interesting answer
amazing what can cause things to tip from an idea to an obsession to see something built 😄
Is it possible to handle coercion failures when using reitit.frontend.easy? (note: I'm aware of :on-coercion-error
in r/match-by-path
, but r.f.e. doesn't really use that). And what'd be the best way to prevent applying controllers until a user is authenticated? Right now I'm finding that it may be easier to dispatch events as pages for my SPA get rendered, as opposed to entering/exiting routes.