Skip to content

registry_paths_resolve

A manifest file enumerates path entries; each must resolve to an on-disk artefact. extract pulls the entry list via a structured query (toml / json / yaml RFC 9535 JSONPath), a line list (lines, optional comment prefix), or a regex capture (regex, group 1). expect (any / file / dir) and must_contain constrain the resolved kind; exclude_query subtracts entries; entries_are_globs expands each entry as a glob. Non-literal entries (interpolation / antiquotation) are skipped, not failed. Optional orphans adds the reverse-completeness check: on-disk artefacts under the space glob that no entry references (the “new crate not wired into the workspace” detector). Cross-file: reads one manifest, resolves against the file index.

- id: workspace-members-resolve
kind: registry_paths_resolve
source: Cargo.toml
extract: { toml: "$.workspace.members[*]" }
expect: dir
must_contain: Cargo.toml
orphans: { space: "crates/*/Cargo.toml", unreferenced: warn }
level: error
OptionTypeRequiredDefaultDescription
basestringResolve entries relative to: registry_dir (default), lint_root, or an explicit path.
entries_are_globsbooleanExpand each extracted entry as a glob rather than treating it as a single literal path; a glob that matches nothing is a violation.
exclude_querystringA structured query selecting entries to subtract from the extracted list before resolution is checked.
expectone of any | file | dirConstrain the kind each entry must resolve to on disk: any (default), file, or dir.
extractobjectyesExactly one of: toml/json/yaml (RFC 9535 JSONPath string), lines (object; optional comment prefix, default #), regex (string; capture group 1 is the path).
must_containstringWhen an entry resolves to a directory, that directory must contain this named child (e.g. Cargo.toml), else the entry is a violation.
orphansobjectEnable the reverse-completeness check: on-disk artefacts under the space glob that no entry references (the “new crate not wired into the workspace” detector).
sourcestringyesThe manifest/registry file (path, or a glob to run once per matching manifest) that enumerates the path entries.

Plus the common level, id, and when fields. This rule analyses the whole repository, so it takes no paths. This table is generated from the JSON Schema; option types and defaults are authoritative.