-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
fix: tag non-stable settings with new system #24287
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please comment and set the PR to Changes Requested if you disagree with any of the new classifications.
@@ -677,7 +675,8 @@ | |||
"scope": "resource", | |||
"type": "boolean", | |||
"tags": [ | |||
"experimental" | |||
"experimental", | |||
"onExP" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just realized that VS Code stable wouldn't recognize the onExP tag, so I'm keeping the experimental tag for now instead of changing it to the new preview tag.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you so much!
after the next VS Code release we can probably remove the experimental
tags, right?
This PR changes some setting tags as follows:
python.missingPackage.severity
setting considering the setting does not seem to be experimental and that the setting does not seem to be part of any experiment.python.locator
setting considering the setting is both experimental (based on its description) and part of an experiment.python.terminal.shellIntegration.enabled
, considering it is a non-stable setting that does not seem to be part of an experiment.python.REPL.sendToNativeREPL
considering it is part of an experiment.