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

Feature request: Change the scope of maven.terminal.customEnv to machine-overridable #991

Open
cypher256 opened this issue Aug 2, 2023 · 1 comment
Labels
feature-request New feature or request

Comments

@cypher256
Copy link

cypher256 commented Aug 2, 2023

Is it possible to change the scope of maven.terminal.customEnv to machine-overridable?
I would like to have remote settings.json updated when vscode.workspace.getconfiguration() is update by an extension in a remote environment such as WSL.

@cypher256 cypher256 changed the title Change the scope of maven.terminal.customEnv to `machine-overridable Change the scope of maven.terminal.customEnv to machine-overridable Aug 2, 2023
@cypher256
Copy link
Author

cypher256 commented Feb 13, 2024

Is it possible to change the maven.executable.path from machine to machine-overridable as the related setting maven.executable.path cannot also be overridden in a workspace?

package.json

"maven.executable.path": {
	"type": "string",
	"scope": "machine" // -> "machine-overridable"
},
"maven.terminal.customEnv": {
	"type": "array",
	"scope": "resource" // -> "machine-overridable"
},

@cypher256 cypher256 changed the title Change the scope of maven.terminal.customEnv to machine-overridable Feature request: Change the scope of maven.terminal.customEnv to machine-overridable Feb 13, 2024
@testforstephen testforstephen added the feature-request New feature or request label Feb 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants