Enum EditCommand 

#[non_exhaustive]
pub enum EditCommand {
    AddRuleSet {
        path: String,
    },
    RemoveRuleSet {
        index: usize,
    },
    UpdateField {
        target: EditTarget,
        path: String,
        value: EditValue,
    },
    SetFallbackRespondDir {
        path: String,
    },
}

A structured edit to apply to the workspace.

Why commands instead of free-form text edits

The brief (§6.1, §6.2) spells this out: free-form text edits are too coarse for a GUI that needs to reason about the change. Commands carry exactly the intent — “add rule set”, “update field at path” — which the apply-layer can validate before writing anything.

Variants (Non-exhaustive)

Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.

AddRuleSet

Add a rule-set file to the workspace.

Fields

path: String

RemoveRuleSet

Remove a rule-set file by its index in the list.

Fields

index: usize

UpdateField

Update an editable field. target identifies which file; path is the dotted TOML path inside that file.

Fields

target: EditTarget

path: String

value: EditValue

SetFallbackRespondDir

Change the fallback respond dir.

Fields

path: String

Trait Implementations

impl Clone for EditCommand

fn clone(&self) -> EditCommand

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for EditCommand

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.