An extension requests workspace trust but the corresponding API is not yet fully supported. Do you want to trust this workspace?

[kittaakos]

Hi there,

I am using git, github, and the github-authentication VSIXs in a Theia-based app. When I start my app, I see the following information message:

An extension requests workspace trust but the corresponding API is not yet fully supported. Do you want to trust this workspace?

Could someone please clarify what this information message means for downstream projects? Does it indicate that API compatibility is not complete (for example, TerminalShellExecutionCommandLine#isTrusted from the compatibility chart)? Or does it suggest that the behavior is undetermined?

Thank you!

[JonasHelming]

@rschnekenbu

[kittaakos]

Hi there 👋

Just following up on this. I know things can get busy, but it's been a while.

This message still appears in our downstream app, and we'd really appreciate any clarification. Even a short explanation would help. It would give us something concrete to tell users and help stakeholders decide whether we should suppress it downstream.

Thanks again!

[msujew]

In my experience it's safe to suppress the info message by simply disabling the feature via the preferences.

[rschnekenbu]

Hi @kittaakos, I do agree with @msujew on that topic.
What this message means in short:

• The workspace trust VS Code API is implemented, so you can request trust for a workspace, store its value and so on, but some of the effects are not yet in place with Theia.
• For example, in VS Code, some extensions are disabled depending on their capabilities if the workspace is not trusted. The navigation for some links may also be disabled. This feature is not yet supported by Theia, e.g. the workspace trust has no effect. So as Mark suggested, you can disable this feature in the settings.