My two cents:
Adding spec inside the original namespace is more readable, provide
documentation just in place, and the user do not need to require a separate
namespace to get spec of your API, I will prefer it.
For users stay in < clojure 1.9.0, I use this macro in my code:
(defmacro
Those are the two obvious options and both are fine. The latter makes
loading and use of the spec optional. If you do that, we recommend putting
specs in the.namespace.specs for the.namespace.
On Friday, September 14, 2018 at 12:00:30 PM UTC-5, Howard M. Lewis Ship
wrote:
>
> I'm thinking of
t: Release a lib w/ specs
I'm thinking of releasing a tiny library (really, just one macro), and I want
to document/validate using spec.
What's the accepted approach for bundling the macro with its spec:
- Just add the spec right in the namespace with the macro
- Have a second optional
I'm thinking of releasing a tiny library (really, just one macro), and I
want to document/validate using spec.
What's the accepted approach for bundling the macro with its spec:
- Just add the spec right in the namespace with the macro
- Have a second optional namespace that provides the spec
