default values missing for workspace.getConfiguration().get in resolver

[aeschli]

On master:

• the test-resolver extension is a UI extension defining a resolver and some configuration options
• In https://github.com/microsoft/vscode/blob/6f1ee4b66cc47b08e523ed8a78291258aa38ad9e/extensions/vscode-test-resolver/src/extension.ts#L29 add

outputChannel.appendLine(JSON.stringify(vscode.workspace.getConfiguration('testresolver').inspect('startupDelay')));
outputChannel.appendLine(JSON.stringify(vscode.workspace.getConfiguration('testresolver').inspect('startupError')));

• run vscode from sources, invoke Remote-TestResolver: New Window
• in the remote window that opens, check the TestResolver output view

  {"key":"testresolver.startupDelay"}
  {"key":"testresolver.startupError"}

  The default values are missing.

Same when accessing workspace.getConfiguration('testresolver).get('startupDelay')

I have the same problem in the Remote WSL extension.

[sandy081]

This is because resolver extensions are activated even before their contributions are scanned.

@alexdima FYI

[sevillal]

@alexdima is there any plan to fix this?

[legomushroom]

Hit this in the GH Codespaces extension recently, since it is a resolver extension, the setting default is not present before the connection is fully established 😊 Worked around this by adding the default in the JS code, not ideal since could diverge with the package.json value at some point, but works for now 👍

[vanowm]

Perhaps if there was some kind of event or promise which we can use to wait for it to finish loading?

[sandy081]

/duplicate

This is now fixed using #224236

[vs-code-engineering[bot]]

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.

Happy Coding!