Skip to content

Properly scope all settings #1629

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

Merged
merged 3 commits into from
Jul 7, 2025
Merged

Conversation

plemarquand
Copy link
Contributor

Be more explicit about settings scopes, marking appropriate ones as application (user settings applied across all swift projects) and machine-overridable (for per-project settings).

@plemarquand plemarquand force-pushed the scope-settings branch 2 times, most recently from 8c9acee to 30e32a7 Compare June 19, 2025 14:07
@@ -782,7 +803,8 @@
"Never automatically update CodeLLDB settings when they are incorrect."
],
"markdownDescription": "Choose how CodeLLDB settings are updated when debugging Swift executables.",
"order": 3
"order": 3,
"scope": "machine-overridable"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe application scope?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the CodeLLDB settings should be per project because its possible some projects may work better with one debugger over the other.

@@ -782,7 +803,8 @@
"Never automatically update CodeLLDB settings when they are incorrect."
],
"markdownDescription": "Choose how CodeLLDB settings are updated when debugging Swift executables.",
"order": 3
"order": 3,
"scope": "machine-overridable"
},
"swift.debugger.useDebugAdapterFromToolchain": {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe application?

@award999
Copy link
Contributor

@plemarquand is their any repercussion if one of the settings we're changing to application is set for the workspace already?

@plemarquand
Copy link
Contributor Author

@award999 Good point, there is a risk that some of the ones being set to "application" will no longer take effect if they're set in a settings.json for a project.

A list of the ones that are now application are:

  • swift.actionAfterBuildError
  • swift.enableTerminalEnvironment
  • swift.showBuildStatus
  • swift.showCreateSwiftProjectInWelcomePage
  • swift.openAfterCreateNewProject

None of these would break a project if they were ignored on a per-project basis, but it might be a bit confusing if they stopped working as they did before.

Be more explicit about settings scopes, marking appropriate ones as
`application` (user settings applied across all swift projects) and
`machine-overridable` (for per-project settings).
@award999
Copy link
Contributor

@plemarquand I think those are low risk settings. Will point it out in release notes and message but I'm not concerned

@award999 award999 removed the up next label Jun 27, 2025
@plemarquand plemarquand merged commit 6fb0818 into swiftlang:main Jul 7, 2025
18 checks passed
@plemarquand plemarquand deleted the scope-settings branch July 7, 2025 13:49
@github-project-automation github-project-automation bot moved this from Next to Needs Verification in Swift Extension for Visual Studio Code Jul 7, 2025
@matthewbastien
Copy link
Member

Verified with 323d996

@matthewbastien matthewbastien moved this from Needs Verification to Done in Swift Extension for Visual Studio Code Jul 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants