Expand description
The collection rules as the project configures them, read from static
files only: Cargo manifests, pytest’s ini/toml sections, package.json
and JSON runner configs, go.mod. A configuration that is code (a
vitest.config.ts) is not evaluated: the rule is unknown there and the
runner’s listing decides.
Structs§
- GoModule
- A Go module: its directory and module path.
- JsPackage
- A JS package: its directory, its runner, and its rule when static.
Functions§
- files
- The files of the checkout (workspace-relative,
/-separated), build output and dependency directories left out. - go_
modules - Every
go.modof the checkout. - go_tags
- The build tags a check sets (
-tags a,b/-tags=a,b). - js_
owner - The JS package a path belongs to.
- js_
packages - Every
package.jsonthat uses vitest or jest (by its scripts or dependencies, or a check naming the runner). - owner
- The package a path belongs to: the one with the longest root above it.
- pytest_
rule - pytest’s rule, from the first configuration file that has a section.
- rust_
packages - Every Cargo package of the checkout (a manifest with
[package]). - uses_
pytest - Whether the project is a pytest project: a pytest configuration, a
conftest.py, or a check that runs pytest. - walk
files, and whether the walk stopped at its limit (the list is then incomplete: nothing can be proved missing from it).