validate-statement-vs-template
functionstemplate->validator
to compile-templates->validators
:selected-templates
profile->validator
to compile-profiles->validators
:selected-profiles
and :selected-templates
validate-statement-vs-profile
to just validate-statement
validate-statement
calls:option
and :result
OCaml-isms to :filter
and :errors
, respectively:all-valid?
kwarg to specify that ALL templates have to match for the statement:short-circuit?
kwarg to specify that only the first validation error should be returnedcompile-patterns->fsms
(note: affects Pattern API):rule
can now also be :prop
or :sref
to distinguish between different types of errors/failures better:vals
field in template error map is now always be a vector, even for Statement Ref errors:determining-property
and :prop-vals
to :det-prop
and :match-vals
, respectively:failure
to :sref-failure
profile->id-template-map
and statement-batch->id-statement-map
convenience fns to the new template.statement-ref
namespace.?statement-ref-opts
a non-optional (albeit nilable) arg for template/create-template-predicate
and template/create-template-validator
.fsm-spec/valid-transition-src-states?
such that source states only have to be a subset, not equals to, the total states.:meta?
to spec for fsm/plus-nfa
.read-next
to work with NFAs as well as DFAs.utils/statement
.statement-ref/get-template-fn
and statement-ref/get-statement-fn
specs to allow for nil
returns and fix arg generation.:every-val-present?
entry to ::template/pred
spec.validator-spec
, create-template-validator
and create-template-predicate
template specs.::persephone/validator-fn
and ::persephone/predicate-fn
spec names.validate-statement-errors
and validate-statement
(for :fn-type :errors
).::persephone/print?
spec for match-statement
.::persephone/error
spec.:selected-profiles
kwarg for compile-profiles->fsms
did not work.:print?
is true) even if it was not the first time that failure was encountered.:nfa-meta
key to the pattern FSMs map (in case meta is lost from :nfa
).s/cat
specs to s/tuple
specs.get-subregistration-id
function in utils.statement
namespace.profile->fsms
match-statement-vs-pattern
match-statement-vs-profile
match-statement-batch-vs-pattern
match-statement-batch-vs-profile
compile-profiles->fsms
, which accepts a coll of Profiles and returns a nested map from Profile ID to Pattern ID to FSM map.match-statement
, which accepts a compiled Profile coll, a state info map (which has been updated; see README for details), a Statement, and an optional :print?
keyword arg.match-statement-batch
, which is the same as above except it accepts a Statement coll.{:error ...}
map instead of throwing an exception upon error.pattern
namespace:
update-children
has been made private.pattern->fsm
has been made private.pattern-tree->fsm
has been renamed to pattern-tree->dfa
.pattern-tree->nfa
has been added.read-visited-templates
has been added.util.profile
, util.statement
, and pattern.errors
namespaces.fsm/read-next
to:
:type
field of the FSM.start-opts
map (currently :record-visit?
is the only accepted field).meta?
argument; if true
, the returned NFAs have a :states
map in the metadata.gen
directory and gentest-specific runnerspattern-validate
and template-validate
fsm
and fsm-spec
to pattern
directoryerrors
to template
directorypredicate
namespaceexplain-data
.pattern-validation/pattern->fsm
.fsm/move-nfa
as a standalone function.fsm/epsilon-closure
now uses transients internally.gen
namespace.gen
namespace to test API functions on statement streams.deps.edn
.match-next-statement
to handle multiple Patterns and Pattern outputs.Can you improve this documentation? These fine people already did:
kelvinqian00 & Kelvin QianEdit on GitHub
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close