Struct DetectorRegistry 

pub struct DetectorRegistry { /* private fields */ }

Registry of registered Detectors. Use DetectorRegistry::with_builtins for the default set, or DetectorRegistry::empty to build from scratch.

Implementations

impl DetectorRegistry

pub fn empty() -> Self

New registry with no detectors. Use add to populate.

pub fn with_builtins() -> Self

New registry preloaded with every detector this crate ships.

pub fn add(&mut self, d: impl Detector + 'static) -> &mut Self

Append a detector.

pub fn remove(&mut self, name: &str) -> usize

Remove every detector whose name() equals name. Returns the number of detectors removed.

pub fn names(&self) -> Vec<&str>

List the names of registered detectors, in registration order.

pub fn project_kinds(&self) -> Vec<KindId>

Collect the project KindIds advertised by registered detectors. Returns deduplicated set in registration order. Detectors that don’t advertise a kind (workspace-only or dynamic) are skipped.

pub fn workspace_kinds(&self) -> Vec<WorkspaceKindId>

Collect the WorkspaceKindIds advertised by registered detectors.

pub fn detect(&self, dir: &Path) -> Vec<DetectorHit>

Run every detector against dir and collect the hits.

Per-facet disambiguation rules:

• Project facet: at most ONE project hit per directory wins — the highest-priority detector across ALL project kinds. Two detectors firing for the same dir (e.g. NodeDetector + BunDetector when both package.json and bun.lock are present) collapse to the higher-priority one (Bun=80 > Node=50).
• Workspace facet: multiple workspace kinds CAN coexist at the same root (Cargo + Npm in a Tauri-style repo). Within the same WorkspaceKindId, the higher-priority detector wins.

A DetectorHit::Both competes on both facets simultaneously.

Trait Implementations

impl Default for DetectorRegistry

fn default() -> Self

Returns the “default value” for a type.