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

hover messages do not work when this plugin is enabled #337

Closed
DetachHead opened this issue Jun 10, 2024 · 6 comments
Closed

hover messages do not work when this plugin is enabled #337

DetachHead opened this issue Jun 10, 2024 · 6 comments
Labels
duplicate This issue or pull request already exists
Milestone

Comments

@DetachHead
Copy link

when the lsp4ij plugin is enabled, error messages do not show up when hovering over underlined code.

when the plugin is disabled:

image

when the plugin is enabled:

image

@angelozerr
Copy link
Contributor

Where comes from this hover?

Could you share your LSP trace https://github.com/redhat-developer/lsp4ij/blob/main/docs/UserGuide.md#lsp-console when you update your file and hover the code.

@DetachHead
Copy link
Author

Where comes from this hover?

sorry i forgot to mention, that diagnostic is one of pycharm's built in inspections, not from the language server.

Could you share your LSP trace https://github.com/redhat-developer/lsp4ij/blob/main/docs/UserGuide.md#lsp-console when you update your file and hover the code.

when i update the file, i see this:
image

when hovering over it, nothing new appears in the traces

@angelozerr
Copy link
Contributor

Please share your full lsp traces

@angelozerr
Copy link
Contributor

Which mapping kind are you using?

Do you create a New file type which could ouverride the existing py file type?

@fbricon
Copy link
Contributor

fbricon commented Jun 10, 2024

With the configuration trick ({}) from #338, I go from PyCharm error hovers:
Screenshot 2024-06-10 at 11 20 24

to PyRight error hovers
Screenshot 2024-06-10 at 11 20 51

@DetachHead
Copy link
Author

thanks! closing this in favor of #338

@DetachHead DetachHead closed this as not planned Won't fix, can't repro, duplicate, stale Jun 10, 2024
@angelozerr angelozerr added this to the 0.0.2 milestone Jun 10, 2024
@angelozerr angelozerr added the duplicate This issue or pull request already exists label Jun 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants