This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-19
Channels
- # announcements (9)
- # babashka (5)
- # babashka-sci-dev (23)
- # beginners (160)
- # calva (78)
- # cider (23)
- # clj-commons (2)
- # clj-kondo (5)
- # cljdoc (19)
- # cljs-dev (8)
- # clojure (54)
- # clojure-australia (1)
- # clojure-czech (2)
- # clojure-dev (17)
- # clojure-europe (8)
- # clojure-italy (8)
- # clojure-nl (2)
- # clojure-sg (3)
- # clojure-uk (4)
- # clojurescript (70)
- # community-development (8)
- # core-async (8)
- # cursive (7)
- # datahike (12)
- # datalog (22)
- # datomic (20)
- # events (1)
- # fulcro (43)
- # graalvm (92)
- # gratitude (5)
- # holy-lambda (77)
- # honeysql (1)
- # jobs (1)
- # lsp (111)
- # membrane (70)
- # nextjournal (13)
- # off-topic (73)
- # pathom (1)
- # polylith (8)
- # portal (32)
- # re-frame (3)
- # reagent (4)
- # reitit (5)
- # releases (2)
- # reveal (4)
- # xtdb (22)
I want to replace an rpc styled api with reitit. Currently all requests are made via POST and a query param e.g. localhost:3000/?action=foo
. Can I set up my routes to cover each option of the action param in one specific route per action, so I'm able to define coercion parameters? Currently my setup doesn't match the route.
["/"
["?action=" {:parameters {:query {:id s/Int}}}
["foo" {:post {:parameters {:form {:x s/Int }}
:handler ::foo }]]]
The request has the path as query-string. So ist it possible to match on the query string?
I also have this solution, but its not possible to create schema definition, as a single function is handling all requests.