Skip to main content

Module fs

Module fs 

Source
Expand description

Filesystem data types shared across the service boundary.

These live in core rather than in filesystem because crate::AppMessage has to carry them: the worker thread produces them and the single state owner consumes them (ARCHITECTURE.md §7.1, §7.2 — core is the shared-types crate). The FileSystemService trait and its implementations stay in filesystem, which re-exports everything here so call sites see one module.

Structs§

DirEntryInfo
One entry in a directory listing.

Enums§

EntryKind
What a directory entry is, determined without following symlinks — a symlink reports as EntryKind::Symlink whatever it points at (ADR-0005 §6).
FsError
Filesystem failures, in the vocabulary the explorer actually needs.
FsEvent
Results sent back from the filesystem worker into the state loop. Exhaustive for the same reason as FsRequest.
FsRequest
Work sent to the filesystem worker thread.

Type Aliases§

FsResult