expose settings in code settings

[FernandoMiguel]

can you expose the settings in vscode settings, instead of having to do it all in the json?

also, what are the default and available options?

"files.associations": {
	"terragrunt.hcl": "terraform",
	"*.tfvars": "terraform",
	"*.tf": "terraform",
	"*.tf.override": "terraform",
},
"files.watcherExclude": {
	"**/.terraform/**": true,
	"**/.terragrunt-cache/**": true
},
"[terraform]": {
	"editor.formatOnSave": true
},
"terraform.languageServer": {
	"enabled": true,
	// "external": true,
	// "args": [
	//     "serve"
	// ]
},

[FernandoMiguel]

bump ?

[paultyng]

We are reworking some of this now (see #423 for one).

Unfortunately VS Code requires these exposed in a certain way to be UI visible, so the names and things need to change to expose it in the UI (it can't be nested) which would be a breaking config change. Not that I don't think we should expose things where possible in the UI, but its not just a simple (ie. editInUI: bool) type change to expose it.

[FernandoMiguel]

breaking change, so v3.0?

[radeksimko]

We plan to do a small overhaul of the extension settings as part of #791 - one of the main motivations is exactly to make all settings easily available through the UI as you mentioned - with that in mind I'm going to close this issue in favour of #791

Existing settings are currently documented under the Readme: https://github.com/hashicorp/vscode-terraform#configuration

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.