Struct SwitchPlan 

pub struct SwitchPlan {
    pub target: ProfileMeta,
    pub outgoing: Option<String>,
    pub sessions: SessionMerge,
    pub scheduled: Option<ScheduledMerge>,
    pub tokens: SavedTokens,
    pub archive: PathBuf,
    pub archive_members: Vec<String>,
    pub restores_desktop_state: bool,
    pub opts: SwitchOpts,
    pub deletions: Vec<DeletionCandidate>,
    pub confirmed_deletions: BTreeSet<DeletionKey>,
    pub prior_synced: Synced,
}

Everything a switch would do, decided before anything is touched.

Fields

target: ProfileMeta

outgoing: Option<String>

The account being switched away from, when it is one we manage.

sessions: SessionMerge

scheduled: Option<ScheduledMerge>

Absent when the target has no known org yet, so there is no history folder to merge into.

tokens: SavedTokens

A switch is only valid with both saved Desktop credential blobs. Mixing a target account’s browser state with the current account’s credential would create an incoherent, destructive half-switch.

archive: PathBuf

archive_members: Vec<String>

restores_desktop_state: bool

opts: SwitchOpts

deletions: Vec<DeletionCandidate>

Schedules an account deleted that others still hold, so this merge would resurrect them. The caller decides — a terminal prompt or the menu bar — and records the verdict in confirmed_deletions.

confirmed_deletions: BTreeSet<DeletionKey>

Type-scoped items the user confirmed should go everywhere. Empty means keep them all, which is also what a non-interactive switch must do.

prior_synced: Synced

Baseline used to plan this switch. Apply combines it with the actual post-write state so unresolved definitions remain unresolved safely.

Trait Implementations

impl Debug for SwitchPlan

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

Formats the value using the given formatter.