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: stub setKeysForSync #10205

Merged
merged 2 commits into from
Sep 30, 2021
Merged

plugin: stub setKeysForSync #10205

merged 2 commits into from
Sep 30, 2021

Conversation

vince-fugnitto
Copy link
Member

What it does

Fixes: #10204.

The commit stubs the method setKeysForSync as it is currently not supported by the framework and likely uses vscode online services to store data across machines.

How to test

  • start the application
  • install eslint or gitlens through the extensions-view
  • confirm there is no activation error due to setKeysForSync

Review checklist

Reminder for reviewers

Signed-off-by: vince-fugnitto [email protected]

@vince-fugnitto vince-fugnitto added the vscode issues related to VSCode compatibility label Sep 30, 2021
@vince-fugnitto vince-fugnitto self-assigned this Sep 30, 2021
The commit stubs the method `setKeysForSync` as it is currently not
supported by the framework and likely uses vscode online services to
store data across machines.

Signed-off-by: vince-fugnitto <[email protected]>
Copy link
Member

@paul-marechal paul-marechal left a comment

Choose a reason for hiding this comment

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

Code LGTM and vscode-eslint works now.

Copy link
Contributor

@marcdumais-work marcdumais-work left a comment

Choose a reason for hiding this comment

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

LGTM - quickly tested and confirmed that the latest available ESLint now activate correctly. GitLens has another issue not related to this stubbed API AFAIK...

Thanks for the quick turn-around @vince-fugnitto !

The commit stubs `ExtensionMode` in order not to fail on activation of
popular extensions (ex: gitlens). The proper implementation should be
done in future iterations.

Signed-off-by: vince-fugnitto <[email protected]>
@vince-fugnitto
Copy link
Member Author

@marcdumais-work I added an additional commit to stub #10201 in order for the gitlens extension (and any extension using ExtensionMode) to successfully activate.

Copy link
Contributor

@marcdumais-work marcdumais-work left a comment

Choose a reason for hiding this comment

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

LGTM - Tested that the second commit allows the latest available GitLens to correctly activate. Awesome!

@vince-fugnitto vince-fugnitto merged commit 3b4e1db into master Sep 30, 2021
@vince-fugnitto vince-fugnitto deleted the vf/stub-settingsSync branch September 30, 2021 20:31
@github-actions github-actions bot added this to the 1.18.0 milestone Sep 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
vscode issues related to VSCode compatibility
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[vscode ext API] GitLens, ESLint: globalState.setKeysForSync is not a function
3 participants