Skip to content

Post-1.0: clean up stale ConfigCommandActionsEnabled UserDefaults key #909

Description

@malpern

#879 removed KanataCommandActionsPolicy and the cmd engine feature entirely. The UserDefaults key it used — "KeyPath.Security.ConfigCommandActionsEnabled" — persists for any user who ran a build that wrote it. Nothing reads it now, so it's benign residue.

Cleanup: a one-line removal during an app migration / first-launch pass:

UserDefaults.standard.removeObject(forKey: "KeyPath.Security.ConfigCommandActionsEnabled")

Low priority, non-blocking for 1.0. Flagged in #879 review so the debt is visible and a future reader who greps for the key (and finds no consumer) understands why it's still in defaults.

Metadata

Metadata

Assignees

No one assigned

    Labels

    post-releasePost-public-1.0 work; not required before stable 1.0 releasetech-debt

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions