pub enum ScopeAxis {
FollowSymlinks,
OneFilesystem,
}Expand description
A scan-scope axis a build may be unable to honour at all.
Not every axis a scan config carries: only the two whose support is a property of the
build rather than of the tree, so asking for one is a request no delivery can carry out
and no stored state can rescue. Which of them this build refuses is stated once, by
ScanConfig::unsupported_axis, and asked there by Request::validate for every route
and by the scan config’s own validation for the engine-internal callers that never build
a request.
Variants§
FollowSymlinks
Walking into what a symbolic link points at.
OneFilesystem
Keeping the walk on the root’s own filesystem.
Implementations§
Source§impl ScopeAxis
impl ScopeAxis
Sourcepub const fn reason(self) -> &'static str
pub const fn reason(self) -> &'static str
Why the axis has no supported semantics, in the library’s field names.
One sentence per axis, and the only one: the engine-internal callers that report
Error::UnsupportedScanConfig print it
verbatim, and RequestError::message prints it with the axis renamed, so no
surface can drift from the rule by rewording its own copy.