Fork me on GitHub

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 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.

Alex Miller (Clojure team)19:04:37

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