This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-10-12
Channels
- # aleph (61)
- # announcements (2)
- # babashka (65)
- # beginners (64)
- # calva (2)
- # clerk (1)
- # cljsrn (1)
- # clojure (60)
- # clojure-austin (7)
- # clojure-europe (13)
- # clojure-italy (2)
- # clojure-losangeles (4)
- # clojure-nl (2)
- # clojure-norway (94)
- # clojure-romania (2)
- # clojure-uk (7)
- # clojuredesign-podcast (5)
- # clojurescript (3)
- # core-typed (2)
- # datomic (42)
- # docker (24)
- # emacs (10)
- # exercism (50)
- # graphql (83)
- # honeysql (25)
- # hyperfiddle (12)
- # malli (13)
- # membrane (49)
- # off-topic (50)
- # podcasts-discuss (1)
- # re-frame (3)
- # reagent (12)
- # reitit (5)
- # releases (2)
- # remote-jobs (8)
❓ Is it possible to only enforce request specs for some calls? (But still use return specs to generate OpenAPI docs?) I'm recommending we use Reitit for an internal project at work, where we're replacing a gRPC API. A concern we have is that as our service has evolved historical data might not be fully conformant with current specs.
Answering myself, as I'm wont to do... The TL;DR is “no”. There's a single https://github.com/metosin/reitit/blob/master/modules/reitit-malli/src/reitit/coercion/malli.cljc#L97-L98 option that affects both requests and responses.
Is there be any appetite for a PR to make that option settable separately for requests and responses? It looks like it should be relatively easy to change the code to do that in a backwards compatible way.
I came up with this: https://github.com/metosin/reitit/pull/656
Kudos for making a very hackable codebase that is easy to contribute to! 🙂