- build-result-map
- check-all-rules-of-type
- check-and-accumulate
- check-and-recur
- check-files!
- check-files-parallel
- check-files-serial
- check-form
- check-pattern
- check-rule
- check-rule-ex-data
- check-single-file
- exception->ex-info
- parse-and-check-file
- prepare-context
- prepare-rules
- resolve-files-from-paths
- run
- run-impl
- runner-error->diagnostic
- update-rules
noahtheduke.splint.runner
Handles parsing and linting all of given files.
Handles parsing and linting all of given files.
check-all-rules-of-typeclj
(check-all-rules-of-type ctx rules parent-form form)For each rule: if the rule is enabled, call check-rule.
If check-rule returns a non-nil result, add or append it to the accumulator.
Otherwise, return the accumulator.
For each rule: if the rule is enabled, call `check-rule`. If `check-rule` returns a non-nil result, add or append it to the accumulator. Otherwise, return the accumulator.
check-and-recurclj
(check-and-recur ctx rules filename parent-form form)Check a given form and then map recur over each of the form's children.
Check a given form and then map recur over each of the form's children.
check-files!clj
(check-files! ctx rules files)Call into the relevant check-path-X function, depending on the given config.
Call into the relevant `check-path-X` function, depending on the given config.
check-formclj
(check-form ctx rules parent-form form)Checks a given form against the appropriate rules then calls on-match to build the
diagnostic and store it in ctx.
Checks a given form against the appropriate rules then calls `on-match` to build the diagnostic and store it in `ctx`.
check-patternclj
(check-pattern ctx rule pattern parent-form form)Call :pattern on the form and if it hits, call :on-match on it.
Only attach parent-form to the metadata after :pattern is true, cuz
parent-form can be potentially massive.
This has implications for pattern writing, where predicates can't rely on that metadata to exist.
Call `:pattern` on the form and if it hits, call `:on-match` on it. Only attach `parent-form` to the metadata after `:pattern` is true, cuz `parent-form` can be potentially massive. This has implications for pattern writing, where predicates can't rely on that metadata to exist.
check-ruleclj
(check-rule ctx rule parent-form form)Rules either have :pattern or :patterns defined, never both.
To avoid iteration and seq manipulation costs, handle them separately.
Use reduced to early exit when checking multiple patterns as we don't
want to create multiple diagnostics for a single form and rule.
Rules either have `:pattern` or `:patterns` defined, never both. To avoid iteration and seq manipulation costs, handle them separately. Use `reduced` to early exit when checking multiple patterns as we don't want to create multiple diagnostics for a single form and rule.
parse-and-check-fileclj
(parse-and-check-file ctx rules filename file)Parse the given file and then check each form.
Parse the given file and then check each form.
runclj
(run args)Convert command line args to usable options, pass to runner, print output.
Convert command line args to usable options, pass to runner, print output.
run-implclj
(run-impl start-time options paths)(run-impl start-time options paths config)Actually perform check
Actually perform check
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close