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

[plugin system] Add stubbed support for proposed extensions.allAcross ExtensionHosts and related APIs #12277

Merged
merged 1 commit into from
Mar 10, 2023

Conversation

marcdumais-work
Copy link
Contributor

@marcdumais-work marcdumais-work commented Mar 9, 2023

What it does

I believe that we do not support multiple extension hosts yet, so this is effectively adding a stubbed version of these proposed vscode APIs, for the benefit of extensions that use them.

At the moment, built-in "vscode.html-language-features" (v1.70.2) does, and will not activate correctly without this.

Fixes #12276

How to test

Here's the extension that I built locally (it's not published yet):
html-language-features-1.70.2.zip

  • unzip the extension and copy it to folder plugins. Remove folder vscode.html-language-features if it exists.
  • start the example application and open a .html file
  • confirm that the extension activate correctly and seems to work
  • confirm that the CQ for the copied content is approved [1]

[1 ] : no IP check necessary in this case. See: https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/7350#note_1090755

Review checklist

Reminder for reviewers

@marcdumais-work marcdumais-work added plug-in system issues related to the plug-in system CQ Required (deprecated) issues requiring a CQ (contributor questionnaire) labels Mar 9, 2023
…ExtensionHosts and related APIs

I believe that we do not support multiple extension hosts yet, so this
is effectively adding a stubbed version of these proposed vscode APIs,
for the benefit of extensions that use them.

At the moment, built-in "vscode.html-language-features" (1.70.2) does,
and will not activate correctly without this.

Fixes #12276

Signed-off-by: Marc Dumais <[email protected]>
marcdumais-work added a commit that referenced this pull request Mar 10, 2023
Some time between 1.66.2 and 1.70.2, the references-view extension
"ms-vscode.references-view" has gone from a standalone extension,
that has its own repository, to a vscode built-in extension, that's
part of the vscode repository. With that change, the extension's
publisher has been updated from "ms-vscode" to "vscode". As of
1.70.2, this extension is referenced in the builtins extension pack
and no longer needs to be specifically referenced in `package.json`.

This PR contains the following:

Example application:
- update the builtin extension pack to v1.70.2
- remove entry for old `references-view` extension
- remove pinning for typescript extensions.
- pin html-language-features to 1.66.2, since v1.70.2 will not work
  until PR #12277 is merged

typescript browser tests:
- use new publisher when referencing `references-view` builtin

Signed-off-by: Marc Dumais <[email protected]>
Copy link
Member

@vince-fugnitto vince-fugnitto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

  • confirmed the bug on master with the plugin
  • confirmed that the changes work as expected with the fix

@marcdumais-work marcdumais-work removed the CQ Required (deprecated) issues requiring a CQ (contributor questionnaire) label Mar 10, 2023
@marcdumais-work marcdumais-work merged commit 4e40790 into master Mar 10, 2023
@marcdumais-work marcdumais-work deleted the md/12276 branch March 10, 2023 17:58
@github-actions github-actions bot added this to the 1.36.0 milestone Mar 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
plug-in system issues related to the plug-in system
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[builtins] [html] r.extensions.allAcrossExtensionHosts is not iterable
2 participants