Skip to content

Consider separating option definition (name, default value) from its storage #62683

@tmat

Description

@tmat

Storage is client specific (e.g. VS settings storage, registry) while an option definition that identifies the option itself is usable across layers. Separation these two concepts would improve layering.

Tracks TODO in code.

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions