What gen-tests shows the model, and the checks its answer must pass before it is written (BOU-572): rc-4 wrote a namespace with invented protocol names that stopped the whole suite from loading. Since BOU-511 its tagged fixtures are checked against their schemas, and with --run it is run, in a separate JVM, before it is written.
What gen-tests shows the model, and the checks its answer must pass before it is written (BOU-572): rc-4 wrote a namespace with invented protocol names that stopped the whole suite from loading. Since BOU-511 its tagged fixtures are checked against their schemas, and with --run it is run, in a separate JVM, before it is written.
(check-errors text {:keys [run?] :as opts})Errors in generated text, or nil. It is read and linted, and its tagged
fixtures checked statically. Only with :run?, and only when those pass,
is it loaded and run, in a separate JVM (run-errors): running the
model's code is opt-in.
Errors in generated `text`, or nil. It is read and linted, and its tagged fixtures checked statically. Only with `:run?`, and only when those pass, is it loaded and run, in a separate JVM (`run-errors`): running the model's code is opt-in.
Environment variables the child keeps: enough to find tools and select the profile, none that hold secrets.
Environment variables the child keeps: enough to find tools and select the profile, none that hold secrets.
(fixture-check text)The tagged fixtures in text checked against their schemas without
evaluating anything: {:errors [line] :unchecked [line]}. A value that is
not literal data cannot be checked that way, so it is reported, not failed.
The tagged fixtures in `text` checked against their schemas without
evaluating anything: {:errors [line] :unchecked [line]}. A value that is
not literal data cannot be checked that way, so it is reported, not failed.(lint-errors text {:keys [root filename context-files]})clj-kondo's warnings and errors for text as the file filename, run from
root the way bb check runs it: the :clj-kondo alias and the project's
.clj-kondo config, with unresolved vars and namespaces raised to errors. context-files are linted alongside so protocol and
arity checks can see the definitions; their own findings are dropped. The
cache is off so the result depends on those files, not on what an earlier
lint happened to leave behind. Returns [line], or nil when clean.
clj-kondo's warnings and errors for `text` as the file `filename`, run from `root` the way `bb check` runs it: the :clj-kondo alias and the project's .clj-kondo config, with unresolved vars and namespaces raised to errors. `context-files` are linted alongside so protocol and arity checks can see the definitions; their own findings are dropped. The cache is off so the result depends on those files, not on what an earlier lint happened to leave behind. Returns [line], or nil when clean.
(missing-namespaces text)One error per namespace text requires that is not on the classpath.
clj-kondo cannot tell an invented namespace from one it has not seen.
One error per namespace `text` requires that is not on the classpath. clj-kondo cannot tell an invented namespace from one it has not seen.
(namespace-api ns-sym){:ns :protocols [{:name :methods [{:name :arglists}]}] :schemas [{:name :form}]
:vars [{:name :arglists}]} for ns-sym, loaded, or {:ns :error} when it
does not load.
{:ns :protocols [{:name :methods [{:name :arglists}]}] :schemas [{:name :form}]
:vars [{:name :arglists}]} for `ns-sym`, loaded, or {:ns :error} when it
does not load.(read-ns-form source)The ns form at the top of source, or nil.
The ns form at the top of `source`, or nil.
(required-namespaces source)The namespaces source requires.
The namespaces `source` requires.
(run-errors text {:keys [root]})Load text and run its tests in a separate JVM on this process's
classpath, the one the namespace check used. Returns [line], or nil when
every tagged fixture matches its schema and every test passes.
The child sees only child-env of this process's environment, so the
provider's API key is not handed to code nobody has read (BOU-572 review).
It is not a sandbox: the code can still reach files and the network.
Load `text` and run its tests in a separate JVM on this process's classpath, the one the namespace check used. Returns [line], or nil when every tagged fixture matches its schema and every test passes. The child sees only `child-env` of this process's environment, so the provider's API key is not handed to code nobody has read (BOU-572 review). It is not a sandbox: the code can still reach files and the network.
(source-file ns-sym)A path clj-kondo can read for ns-sym's source, or nil. A source inside a
jar is copied out to a temporary file. Clojure's own namespaces are left
out: kondo knows them, and clojure.core is large.
A path clj-kondo can read for `ns-sym`'s source, or nil. A source inside a jar is copied out to a temporary file. Clojure's own namespaces are left out: kondo knows them, and clojure.core is large.
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |