leona.schema — workshub/leona 0.2.2

*context* clj

accept-spec clj multimethod

accept-spec-wrapper clj

(accept-spec-wrapper dispatch spec children {:keys [custom-scalars] :as opts})

We use this function to intercept calls to 'accept-spec' and skip certain specs (e.g. where they are custom scalars)

clean-extracted-object clj

(clean-extracted-object d k)

combine clj

(combine & specs)

combine-with-opts clj

(combine-with-opts opts & specs)

find-invalid-key clj

(find-invalid-key m)

(find-invalid-key m path)

fix-references clj

(fix-references schema options)

list clj

(list t s)

(list t s nn?)

make-optional-fields clj

(make-optional-fields fields spec)

(make-optional-fields fields opt opt-un)

non-null clj

(non-null t)

remove-non-null clj

(remove-non-null f)

spec-name-or-alias clj

(spec-name-or-alias spec {:keys [type-aliases]})

spec-resolves-to-set? clj

(spec-resolves-to-set? spec)

transform clj

(transform spec)

(transform spec options)

valid-replacement-type? clj

(valid-replacement-type? t)

valid-type-override-syms clj

These symbols can be used to wrap types when using st/spec, e.g. (st/spec my-date-pred? {:type '(custom :date)}). They only exist separately to provide semantic information - it's not asserted anywhere that the types they reference ever exist anywhere so USE WITH CAUTION.