Struct ExcludeMatchers 

pub struct ExcludeMatchers {
    pub invalid: Vec<(String, String)>,
    /* private fields */
}

Compiled exclude patterns with directory-pattern expansion applied.

Match paths through matched_pattern using a root-relative path (the CLI relativizes against the project root, the LSP against the containing workspace root) so patterns like docs/drafts behave identically everywhere.

Fields

invalid: Vec<(String, String)>

Patterns that failed to compile, with their errors. Callers decide how to surface these (CLI prints to stderr, LSP logs).

Implementations

impl ExcludeMatchers

pub fn new(patterns: &[String]) -> Self

Compile patterns to exclude what the discovery walk excludes.

The walk applies each pattern as an ignore override, which reads it the way .gitignore does, so a file named directly has to be matched by the same rules or it is linted where the walk skips it:

• A pattern with no / except a trailing one matches at any depth: node_modules excludes packages/app/node_modules/readme.md.
• A pattern that matches a directory excludes everything in it, including one whose final component is a wildcard: draft? excludes drafts/note.md.
• * and ? match within one path component: sub/*.md excludes sub/top.md but not sub/a/b.md.

Relative patterns are otherwise anchored at the root the path is relative to, and an absolute pattern never floats.

pub fn is_empty(&self) -> bool

pub fn matched_pattern(&self, relative_path: &str) -> Option<&str>

The first pattern matching relative_path, if any.

pub fn is_match(&self, relative_path: &str) -> bool

pub fn matched_pattern_for_file( &self, relative: Option<&str>, absolute: &Path, ) -> Option<&str>

The first pattern matching a file, if any.

Both forms of the file are tried: its relative form (how patterns are normally written - relative to the project or workspace root) and its absolute path, which is what an absolute pattern matches. Absolute patterns reach config either written literally or through ~ expansion, and the walker’s overrides cannot apply them (the ignore crate anchors a leading / to the walk root), so this is where they take effect.

Only absolute patterns are matched against the absolute path. A relative pattern belongs to the root its path is relative to, and one that floats would otherwise match a directory above that root: docs would exclude every file of a project checked out at /home/dev/docs/site.

absolute is canonicalized before matching, since an expanded ~ resolves to a canonical location. A file that does not exist (an unsaved buffer, one already deleted) is resolved through its deepest existing ancestor (see resolve_for_matching).

The path as given is tried as well, because resolving can respell a location the pattern names directly: on macOS /home canonicalizes to /System/Volumes/Data/home, which /home/dev/** does not match.

A pattern that named its location through a symlink (/var/folders/** for a macOS temp directory) never matches that canonical form, so the file’s other spellings are tried too (see PathAliases).

pub fn excludes_file(&self, relative: Option<&str>, absolute: &Path) -> bool

Whether any pattern matches the file (see matched_pattern_for_file).