#[non_exhaustive]pub struct RenumberResult {
pub from: u32,
pub to: u32,
pub no_op: bool,
pub renamed_file: Option<(PathBuf, PathBuf)>,
pub frontmatter_updated: bool,
pub h1_updated: bool,
pub updated_references: Vec<PathBuf>,
pub prose_warnings: Vec<PathBuf>,
pub ambiguous_references: Vec<PathBuf>,
}Expand description
Describes what Repository::renumber changed (or, with dry_run: true,
would change) so the caller can print a plan or a report without needing
to inspect the filesystem itself.
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.from: u32The source number.
to: u32The destination number.
no_op: boolTrue when from == to; every other field is left at its default.
renamed_file: Option<(PathBuf, PathBuf)>The renumbered record’s old and new file paths.
frontmatter_updated: boolTrue when the record’s own frontmatter number field was rewritten
(nextgen mode only).
h1_updated: boolTrue when the record’s own H1 heading was rewritten. Nygard-style
templates number the H1 (# 3. Title); MADR’s bare # Title has no
number and is never rewritten.
updated_references: Vec<PathBuf>Paths of other records whose inbound references (frontmatter
links[].target and/or a rendered body markdown link) were rewritten
to point at to instead of from.
prose_warnings: Vec<PathBuf>Paths outside the ADR directory that still mention the old filename. Informational only – never rewritten.
ambiguous_references: Vec<PathBuf>Paths of records holding a frontmatter links[].target equal to from
that were deliberately left alone because from was a duplicate, so
the reference could have meant either record. Informational only.
Trait Implementations§
Source§impl Clone for RenumberResult
impl Clone for RenumberResult
Source§fn clone(&self) -> RenumberResult
fn clone(&self) -> RenumberResult
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more