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

Setting to None clears all of my previous choices #199413

Closed
TylerLeonhardt opened this issue Nov 28, 2023 · 3 comments
Closed

Setting to None clears all of my previous choices #199413

TylerLeonhardt opened this issue Nov 28, 2023 · 3 comments
Assignees
Labels
extensions Issues concerning extensions *out-of-scope Posted issue is not in scope of VS Code under-discussion Issue is under discussion for relevance, priority, approach
Milestone

Comments

@TylerLeonhardt
Copy link
Member

Testing #199180

  1. Hit Auto Update & Auto Update All on a few extensions
  2. Now set the setting to None (expectedly, the choices before are unchecked)
  3. Now switch the setting back to SelectedExtensions
  4. 🐛 my previous choices are all gone

Imagine I have set auto update on a bunch of extensions & publishers that my company trusts... but because I'm trying to troubleshoot something, or I'm working under crunch time and don't want anything about my environment to change for a bit, I switch to None.

Now at this point, I've lost all of my previous preferences and I have to redo everything again. This is a bit frustrating. I would expect that either:

  • my previous preferences would be re-applied or,
  • when setting to None, a modal pops up saying all my selected choices will get clobbered
@sandy081
Copy link
Member

Thanks for the feedback.

when setting to None, a modal pops up saying all my selected choices will get clobbered

I would prefer this option. I will wait for more feedback and see what users are expecting in general,

@sandy081 sandy081 added extensions Issues concerning extensions under-discussion Issue is under discussion for relevance, priority, approach labels Nov 28, 2023
@sandy081 sandy081 added this to the Backlog milestone Nov 28, 2023
@isidorn
Copy link
Contributor

isidorn commented Nov 29, 2023

Got hit by exactly this issue. From those two options, I think this one makes a strictly better user experience:

previous preferences would be re-applied

@sandy081 sandy081 added the *out-of-scope Posted issue is not in scope of VS Code label Dec 15, 2024
Copy link

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding, and happy coding!

@vs-code-engineering vs-code-engineering bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
extensions Issues concerning extensions *out-of-scope Posted issue is not in scope of VS Code under-discussion Issue is under discussion for relevance, priority, approach
Projects
None yet
Development

No branches or pull requests

3 participants