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

Change configurations to window scope #686

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

apetresc
Copy link

@apetresc apetresc commented Mar 4, 2021

At the moment, all leetcode-specific preferences have scope set to application, which means they can only be set in a user's global settings.json. I think it makes much more sense to have them window scoped, which basically means you can set them in your workspace's .vscode/settings.json (you can also still have base settings in your user's settings.json too; they are simply overridden by workspace-specific ones).

Most people have a single workspace/repo for their leetcode contest problems, and it makes a lot more sense to allow them to sync their vscode-leetcode settings directly in that repository, instead of asking them to pollute their system-wide settings.json for a niche extension that only really makes sense in the context of a single workspace.

(Documentation on preference scopes)

At the moment, all leetcode-specific preferences have scope set to `application`, which means they can _only_ be set in a user's global `settings.json`. I think it makes much more sense to have them `window` scoped, which basically means you can set them in your workspace's `.vscode/settings.json` (you can _also_ still have base settings in your user's `settings.json` too; they are simply overridden by workspace-specific ones).

Most people have a single workspace/repo for their leetcode contest problems, and it makes a lot more sense to allow them to sync their `vscode-leetcode` settings directly in that repository, instead of asking them to pollute their system-wide `settings.json` for a niche extension that only really makes sense in the context of a single workspace.

([Documentation on preference scopes](https://code.visualstudio.com/api/references/contribution-points#contributes.configuration))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant