This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-11
Channels
- # aws (6)
- # beginners (167)
- # cider (41)
- # cljs-dev (6)
- # cljsrn (3)
- # clojure (399)
- # clojure-dusseldorf (1)
- # clojure-nl (2)
- # clojure-spec (3)
- # clojure-uk (47)
- # clojurescript (16)
- # core-async (8)
- # cursive (56)
- # datomic (14)
- # devcards (1)
- # docs (2)
- # duct (2)
- # editors (3)
- # emacs (3)
- # fulcro (178)
- # graphql (10)
- # off-topic (107)
- # onyx (7)
- # pedestal (21)
- # planck (13)
- # re-frame (58)
- # reagent (76)
- # ring-swagger (3)
- # shadow-cljs (85)
- # slack-help (2)
- # sql (1)
- # tools-deps (11)
- # uncomplicate (5)
- # vim (24)
- # yada (4)
What’s the least wrong way of tightening a spec in the registry in the context of another spec?
For example, I’m writing specs for config maps in general, and for config maps for production. The general spec for e.g. :config.mode
might be #{:app :lib}
but when it appears in my :config.prod
spec, I’d like to further constrain it to be simply #{:lib}
.
s/and
with predicates is a perfectly adequate way to do this, but I seem to recall a better way.
s/and is what I would say
It makes generating values unlikely, but this is also a case where I really don’t care about that