Skip to content

Where possible, invalid keys should be reset to the default, rather than resetting the whole config. #14424

Closed
Closed
Where possible, invalid keys should be reset to the default, rather than resetting the whole config.#14424
Labels
feature/configurationMaking NVDA more configurable.p3https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.
@cary-rowen

Description

@cary-rowen
cary-rowen
opened on Dec 6, 2022

Is your feature request related to a problem? Please describe.

Related to #14412
While downgrades are not supported, we should take this into account and never assume that users will do certain things exactly as we expect them to.

Describe the solution you'd like

When upgrading the config, backups should be should kept for each schema version (e.g. just before upgrading, and just after upgrading).
This will allow for better downgrading and upgrading.

Describe alternatives you've considered

None

Additional context

None

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature/configurationMaking NVDA more configurable.p3https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions