(add-spec-to-ext-rule-fn profiles rng extension-rule)
When extension-rule
is describing a context or result extension, continue on to in-line-schema->spec
,
otherwise return extension-rule
unaltered
When `extension-rule` is describing a context or result extension, continue on to `in-line-schema->spec`, otherwise return `extension-rule` unaltered
(containsv? coll query)
does coll
contain query
?
does `coll` contain `query`?
(derive-generation-hint profiles rng template-rules)
attempt to determine extension spec that's more accurate than :com.yetanalytics.datasim.json/any
-> if such a spec is derived, will be added to the rule at the key :spec
-> requires an s/gen
to be created from the derived spec in order to replace :com.yetanalytics.datasim.json/any
attempt to determine extension spec that's more accurate than `:com.yetanalytics.datasim.json/any` -> if such a spec is derived, will be added to the rule at the key `:spec` -> requires an `s/gen` to be created from the derived spec in order to replace `:com.yetanalytics.datasim.json/any`
(extension-concept-from-profiles profiles ext-id)
search profiles
for a concept with id = ext-id
search `profiles` for a concept with id = `ext-id`
(filter-for-extension-rule-fn a-rule)
parsed :location
needs to indicate the rule is about an extension
parsed `:location` needs to indicate the rule is about an extension
(filter-for-extension-rules template-rules)
return rules for the current template which specify a context or result extension but don't provide any generation hints within the rule itself
return rules for the current template which specify a context or result extension but don't provide any generation hints within the rule itself
(filter-for-extension-rules* template-rules)
filter template-rules
for rules targeting an extension
filter `template-rules` for rules targeting an extension
(filter-for-rel-ext-rules-fn ext-rule)
only care about rules which provide no additional info to go off of in majority of cases
only care about rules which provide no additional info to go off of in majority of cases
(in-line-schema->spec profiles rng raw-rule parsed-loc)
When an inlineSchema
is found for an extension referenced by raw-rule
:
s/spec
via jschema/schema->spec
s/spec
can be the basis of a s/gen
The s/spec
is only added to raw-rule
at :spec
if a generator can be created from it via s/gen
,
otherwise return raw-rule
unaltered and rely on default of com.yetanalytics.datasim.json/any
When an `inlineSchema` is found for an extension referenced by `raw-rule`: 1) use the JSON Schema to create a `s/spec` via `jschema/schema->spec` 2) determine if the `s/spec` can be the basis of a `s/gen` The `s/spec` is only added to `raw-rule` at `:spec` if a generator can be created from it via `s/gen`, otherwise return `raw-rule` unaltered and rely on default of `com.yetanalytics.datasim.json/any`
(search-profile-for-extension ext-id profile)
filter :concepts
within profile
for one with id = ext-id
filter `:concepts` within `profile` for one with id = `ext-id`
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close