-
Notifications
You must be signed in to change notification settings - Fork 1.9k
fix: add multi-token mapping support to hovers #10233
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
Conversation
|
Turns out making hover more resilient for this is a bit trickier, but supporting this on a basic level should be fine for the time being I'd say. Another nit I just realized, the type hover fallback shouldn't be included here by default I feel like as this might become a bit messy with some macros to read the hover of. That is, only if we do not get any hover info for any of the descended tokens we want to show the fallback, otherwise just ignore a descended token if it doesn't resolve to anything. Doesn't need to be addressed in this PR now though as this might be a bit annoying to do, might be good to add a note/fixme for that still. |
d36113c to
362fa49
Compare
(the PR has been updated to address this) |
362fa49 to
432c6ba
Compare
|
Also side note, we disallow merge commits, hence the failing tests. |
good to know! I'll rebase once all other issues with this PR are resolved. |
# This is the 1st commit message: add multi-token mappings for hover # The commit message rust-lang#2 will be skipped: # make fallback an Option instead of vec # The commit message rust-lang#3 will be skipped: # fix indentation
8eb45f1 to
45090e4
Compare
|
Looks good to me now, thanks! |
implement #10070 in
hover