Skip to content

Design custom scan excludes in settings #160

Description

@Muawiya-contact

Goal

Design and add a small settings surface for scan excludes.

Diskern has default excluded paths like /proc, /sys, and system folders. Advanced users may want to add their own folders that should never be walked.

Why this is advanced

This touches safety and scan authority. A bad design could make a scan silently skip too much or make results confusing.

Current code pointer

Defaults are here:

fn default_excludes() -> Vec<String> {
    let mut v = vec![];
    #[cfg(target_os = "linux")]
    v.extend(["/proc", "/sys", "/dev", "/run"].map(String::from));
    v
}

File:

crates/diskern-core/src/scanner.rs

Suggested approach

Start with a short design comment in the issue or PR before coding:

  • where custom excludes are stored
  • how the UI explains them
  • how a user resets them
  • how tests prove excluded scan roots still fail clearly

Acceptance criteria

  • Custom excludes are explicit and visible to the user.
  • Excluding a chosen scan root still produces a clear error.
  • Tests cover at least one custom exclude case.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appThe Tauri desktop apparchitectureWorkspace layout and engine designenginediskern-core: scanner, rules, risk, graph, reportenhancementNew feature or requesthelp wantedExtra attention is neededlevel: advancedCross-cutting or safety-critical design workpriority: mediumWorth doing, not urgentsafetyTouches the read-only / quarantine guarantees

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions