Liking cljdoc? Tell your friends :D
Mostly clj/s.
Exceptions indicated.

com.fulcrologic.guardrails.core


<-clj/s

source

=>clj/s

source

>defclj/smacro

(>def k spec-form)
(>def k _doc spec-form)

Simple pass-through to s/def, except it strips the specs in production – use for data specs you don't need in production when you want to minimise your build size.

You can optionally send a documentation string as the second parameter, this is intended to be informational for the code reader, current this is not stored anywhere, meaning you can't access this string at runtime.

Simple pass-through to `s/def`, except it strips the
specs in production – use for data specs you don't need
in production when you want to minimise your build size.

You can optionally send a documentation string as the second parameter, this
is intended to be informational for the code reader, current this is not stored
anywhere, meaning you can't access this string at runtime.
sourceraw docstring

>defnclj/smacro

(>defn name
       doc-string?
       attr-map?
       ([params*] gspec prepost-map? body?)
       +
       attr-map?)
(>defn name doc-string? attr-map? [params*] gspec prepost-map? body?)

Like defn, but requires a (nilable) gspec definition and generates additional s/fdef, generative tests, instrumentation code, an fspec-based stub, and/or tracing code, depending on the configuration metadata and the existence of a valid gspec and non-nil body.

Like defn, but requires a (nilable) gspec definition and generates
additional `s/fdef`, generative tests, instrumentation code, an
fspec-based stub, and/or tracing code, depending on the configuration
metadata and the existence of a valid gspec and non-nil body.
sourceraw docstring

>defn-clj/smacro

(>defn- name
        doc-string?
        attr-map?
        ([params*] gspec prepost-map? body?)
        +
        attr-map?)
(>defn- name doc-string? attr-map? [params*] gspec prepost-map? body?)

Like defn-, but requires a (nilable) gspec definition and generates additional s/fdef, generative tests, instrumentation code, an fspec-based stub, and/or tracing code, depending on the configuration metadata and the existence of a valid gspec and non-nil body.

Like defn-, but requires a (nilable) gspec definition and generates
additional `s/fdef`, generative tests, instrumentation code, an
fspec-based stub, and/or tracing code, depending on the configuration
metadata and the existence of a valid gspec and non-nil body.
sourceraw docstring

>fdefclj/smacro

(>fdef name [params*] gspec)
(>fdef name ([params*] gspec) +)

Defines an fspec using gspec syntax – pretty much a >defn without the body.

name can be a symbol or a qualified keyword, depending on whether the fspec is meant to be registered as a top-level fspec (=> s/fdef fn-sym ...) or used in other specs (=> s/def ::spec-keyword (s/fspec ...)).

Defines an fspec using gspec syntax – pretty much a `>defn` without the body.

`name` can be a symbol or a qualified keyword, depending on whether the
fspec is meant to be registered as a top-level fspec (=> s/fdef fn-sym
...) or used in other specs (=> s/def ::spec-keyword (s/fspec ...)). 
sourceraw docstring

?clj/smacro

(? & forms)
source

clean-defnclj

(clean-defn op forms)

This removes the gspec and returns a clean defn for use in production builds.

This removes the gspec and returns a
clean defn for use in production builds.
sourceraw docstring

run-checkclj/s

(run-check args? {:keys [log-level vararg? throw? fn-name]} spec value)
source

|clj/s

source

cljdoc is a website building & hosting documentation for Clojure/Script libraries

× close