-
Notifications
You must be signed in to change notification settings - Fork 35
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
Tooltips for .:, .:? and etc don't work #184
Comments
The leading dot might be causing confusion with module separators, yes |
Is there opportunity to use the CST lexer to normalize handling of things like this? I can understand why you might not want to include the dependency, but it might help with edge cases like this. |
Probably, the current code is in a hard to understand place because it's driven by the need to match the (qualified) identifier around the cursor - it does some weirdness in separately matching regexes before and after the cursor, when probably it should just tokenize the current line (I guess things that are split over lines are still fine at a lexical level) and compare the cursor position with the result of that I note that for qualified imports |
This is only problematic for string literals, but otherwise qualified names cannot contain whitespace. |
Same issue as nwolverson/purescript-language-server#146 |
Linked issue is fixed since 0.15.5 (which is already in the current ide-purescript release) |
Hey and thanks for all the good work done on the plugin!
I'm using argonaut that has a couple of operators like ".:" and for some reason tooltips don't work on those operators (perhaps it has something to do with the way these are - the leading dot may be causing the confusion?)
While tooltips seem to appear for <> or ~> or other operators.
I'm using the latest plugin version, and VSCode "Version: 1.59.0-insider (Universal) Commit: 379476f0e13988d90fab105c5c19e7abc8b1dea8"
Hope that helps :)
PS Jump to definition doesn't work either on the above mentioned operators, might be somehow related to the problem.
The text was updated successfully, but these errors were encountered: