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

Improvement global status item in VS Code Java to be more user friendly #3473

Closed
nickzhums opened this issue Jan 22, 2024 · 2 comments · Fixed by #3478
Closed

Improvement global status item in VS Code Java to be more user friendly #3473

nickzhums opened this issue Jan 22, 2024 · 2 comments · Fixed by #3478

Comments

@nickzhums
Copy link
Contributor

nickzhums commented Jan 22, 2024

Here to suggest two improvements of global status item for VS Code Java

Item 1 - Currently, the tooltip of global status item in VS Code Java shows "ServiceReady". This is a bit generic to the user and does not indicate it is relevant to the Java language server. Suggest to update the tooltip to "Java Language Server Ready".

image

Item 2 - We are not recording the telemetry of how many users has clicked this icon, thus unable the analyze the usage and effectiveness. Therefore to suggest record the telemetry

@rgrunber
Copy link
Member

public setReady(): void {
this.statusBarItem.text = StatusIcon.ready;
this.statusBarItem.command = Commands.SHOW_SERVER_TASK_STATUS;
this.statusBarItem.tooltip = "ServiceReady";
}

Seems like the tooptip could just use a better value.

Another consideration is whether we can do something about #3416 (comment) . Are there instances where it makes sense to hide (StatusBarItem.hide()) it or are we committed to always showing it if some project has triggered the import.

@rgrunber rgrunber added the ux label Jan 22, 2024
@nickzhums
Copy link
Contributor Author

nickzhums commented Jan 23, 2024

Yes, for item 1 we can just update the tooltip.

@rgrunber rgrunber linked a pull request Jan 26, 2024 that will close this issue
@rgrunber rgrunber added this to the End January 2024 milestone Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants