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

Adopt new createStatusBarItem API #2083

Merged
merged 1 commit into from
Oct 19, 2021

Conversation

jdneo
Copy link
Collaborator

@jdneo jdneo commented Aug 24, 2021

resolve #1982

Here is the appearance in standard mode
WeChat Screenshot_20210824163918

Here is the appearance in Lightweight mode
WeChat Screenshot_20210824163941

Signed-off-by: Sheng Chen [email protected]

@Eskibear
Copy link
Contributor

LGTM.

Current it's showing extension name instead of a meaningful name of the item, as shown below:
image

@rgrunber
Copy link
Member

Is it possible to maintain support with 1.53.2 while adopting this change (ie. not bumping up?). Similar to https://github.com/redhat-developer/vscode-java/pull/1975/files .

@fbricon , I think Theia is still on 1.50.0, and likely doesn't support this new API.

@fbricon
Copy link
Collaborator

fbricon commented Aug 25, 2021

probably, but that requires guarding against the unavailable APIs

@jdneo
Copy link
Collaborator Author

jdneo commented Sep 23, 2021

The new createStatusBarItem() is an overload method, which I guess we need to use the version field to check which version of the API should be used. Do you think this is accpetable? (we may need to introduce a new npm module: semver to do the version comparing)

@rgrunber
Copy link
Member

rgrunber commented Sep 24, 2021

The new createStatusBarItem() is an overload method, which I guess we need to use the version field to check which version of the API should be used. Do you think this is accpetable? (we may need to introduce a new npm module: semver to do the version comparing)

I guess if this is the only way to approach this, we'd have to do it. It seems to already be a transitive dependency of other requirements we have.

In the future, we can also use https://che-incubator.github.io/vscode-theia-comparator/status.html to track API differences for things we may want to adopt.

@jdneo
Copy link
Collaborator Author

jdneo commented Sep 26, 2021

Cool table for API tracking, thanks!

@rgrunber rgrunber self-requested a review September 29, 2021 12:18
Copy link
Member

@rgrunber rgrunber left a comment

Choose a reason for hiding this comment

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

Just a few changes to make so that this change is compatible with 1.53. Otherwise, I can confirm it works in VS Code.

@rgrunber rgrunber added this to the Mid October 2021 milestone Oct 18, 2021
@jdneo
Copy link
Collaborator Author

jdneo commented Oct 19, 2021

@rgrunber Thanks it works for me as well. I just updated the PR.

@rgrunber rgrunber merged commit 3eaac3a into redhat-developer:master Oct 19, 2021
@jdneo jdneo deleted the cs/issue-1982 branch October 19, 2021 03:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Consider to adopt new createStatusBarItem API for id and name properties
4 participants