-
Notifications
You must be signed in to change notification settings - Fork 11
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
feat: inlay hints #38
Conversation
@willothy can you give this one a look over as there is a lot here i think its good to go though |
I'll look this over tomorrow! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, just a few small edits. I might be wrong about the has()
thing if the inlay_hint API is different between 0.10 and 0.11.
local M = {} | ||
|
||
function M.inlay_hints_enabled(t) | ||
if vim.lsp and vim.lsp.inlay_hint and vim.lsp.inlay_hint.is_enabled then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couldn't you use has("nvim-0.10")
here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this isn't a big deal then this PR is good to merge once conflicts are handled imo :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I need to rebase and will check the field name. I know the lsp API changed a few times in 0.10. I can't remember which released
I will check docs tomorrow
Needs:
Test WS offsetoffsets need some adjustments as on complex lines they get messed upCloses #37