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

vscode: align typings for provideHover #11862

Merged
merged 1 commit into from
Nov 11, 2022

Conversation

planger
Copy link
Contributor

@planger planger commented Nov 11, 2022

What it does

Aligns the typings of HoverProvider.provideHover with the API of VS Code.
This change also updates the documentation to include the token parameter in the signature of the hover provider examples. Technically, this isn't necessary, but for the sake of completeness, I thought it makes sense.

Fixes #11827

Contributed on behalf of STMicroelectronics

How to test

This isn't really a breaking change and only impacts the external extension API, which isn't used directly (I assume) anyway, as people most likely implement against the VS Code API anyway. Also, this method is never invoked directly from within Theia too. So there is nothing really to test, imho.

I locally confirmed that this change makes the report happy.

Review checklist

Reminder for reviewers

Fixes eclipse-theia#11827

Contributed on behalf of STMicroelectronics

Change-Id: I328a77cb1a795ada070e11ba3668a96fec00a354
Signed-off-by: Philip Langer <[email protected]>
@planger planger force-pushed the planger/issues/11827 branch from 284159a to e7a1145 Compare November 11, 2022 13:11
Copy link
Member

@msujew msujew left a comment

Choose a reason for hiding this comment

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

I can confirm that this change correctly aligns the typing for the provideHover method, as indicated by the vscode comparator report.

@msujew msujew merged commit 432ee41 into eclipse-theia:master Nov 11, 2022
@vince-fugnitto vince-fugnitto added the vscode issues related to VSCode compatibility label Nov 24, 2022
@vince-fugnitto vince-fugnitto added this to the 1.32.0 milestone Nov 24, 2022
@planger planger deleted the planger/issues/11827 branch February 3, 2023 09:13
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: update typings for provideHover
3 participants