Reload config when sfdx-project change

[Bartheleway]

Working with replacement strings or just changing the sourceApiVersion property in sfdx-project.json I noticed the extension doesn't take into account the changes until I reload them or restart VS Code. It could be very nice to have an observer on config change so that extension always use updated version. This would be especially usefull when switching between branches which doesn't have the same sfdx-project.json config.

[peternhale]

More detail

Hi, here is an example sfdx-project.json

{
	"packageDirectories": [
		{
			"path": "force-app",
			"default": true
		}
	],
	"namespace": "",
	"sfdcLoginUrl": "https://login.salesforce.com",
	"sourceApiVersion": "64.0",
	"replacements": [
		{
			"glob": "force-app/main/default/authproviders/*.authprovider-meta.xml",
			"stringToReplace": "#AUTH_EXECUTION_USER#",
			"replaceWithEnv": "ENV_AUTH_EXECUTION_USER",
		},
		{
			"filename": "force-app/main/default/authproviders/SomeAuthProvider.authprovider-meta.xml",
			"stringToReplace": "#AUTH_CLIENT_ID#",
			"replaceWithEnv": "ENV_AUTH_CLIENT_ID",
		}
	]
}

Indeed having VS Code to ask for environment variable when missing is a feature request. VS Code extension not loading the latest environment vars state is I think a bug.

You might find that awkward but I assure you this is a real use case. Unfortunately in some precise spot Salesforce use hardcoded ids (or other not stable values) in metadata which oblige us to us replacement strings to correctly handle the different values we have based on the environment. When in dev sandbox, we use VS Code extensions to push changes. As it is development we might want to use a specific value to make a specific test. Also some of replacement values are secret and store on a remote vault that cannot be accessed on dev computer and therefore we provide dummy values (but respecting format) for them, they cannot be blank.