Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
Tracked by #58717
tmat opened this issue Jul 15, 2022 · 1 comment
Closed
Tracked by #58717

Comments

@tmat
Copy link
Member

tmat commented Jul 15, 2022

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.

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead labels Jul 15, 2022
@tmat tmat self-assigned this Jul 15, 2022
@tmat tmat added Concept-Continuous Improvement and removed untriaged Issues and PRs which have not yet been triaged by a lead labels Jul 15, 2022
@tmat tmat added this to the Backlog milestone Jul 15, 2022
@tmat tmat mentioned this issue Jul 15, 2022
73 tasks
@CyrusNajmabadi
Copy link
Member

@tmat i'm closing this out as i thought you did this. reactivate if i'm wrong.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants