This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-08-07
Channels
- # aleph (4)
- # announcements (7)
- # arachne (1)
- # beginners (138)
- # calva (5)
- # cider (1)
- # clara (14)
- # clj-kondo (1)
- # cljsrn (2)
- # clojars (4)
- # clojure (247)
- # clojure-dev (33)
- # clojure-europe (3)
- # clojure-italy (71)
- # clojure-losangeles (6)
- # clojure-romania (6)
- # clojure-spain (11)
- # clojure-uk (17)
- # clojurescript (95)
- # core-async (2)
- # cursive (19)
- # datomic (7)
- # duct (27)
- # figwheel (1)
- # graalvm (22)
- # juxt (7)
- # kaocha (8)
- # leiningen (1)
- # luminus (7)
- # lumo (4)
- # off-topic (38)
- # reagent (4)
- # reitit (11)
- # shadow-cljs (30)
- # spacemacs (42)
- # tools-deps (103)
- # xtdb (5)
any ideas to provide default values for path parameters?
I would prefer to provide default values as part of coercion
@faisalhasnain90 Schema-tools supports defaults as part of the coercion, spec (or spec-tools) doesn’t.
Thanks 🙂 i wish spec-tools provide this functionality out of box. Any plans in future?
no plans, but help most welcome: https://github.com/metosin/spec-tools/issues/51
might try in spare time in future 🙂
ok, started to develop metosin/malli
brcause these things are really hard to add to spec, as it doesn’t support any value transformation by default.
spec-tools has lot of small issues that are hard to fix. nothing critical, but still.
make sense, perhaps future version of clojure spec becomes more powerful/flexible to support such use cases.