We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The language server introduces NA when code like the following occurs
function() { test <- print( }
This causes for the Neovim lsp interface to error out. In this like shiny this is a very common thing to find.
My fix was pretty easy, I went to the code_point_to_unit function and added the following:
code_point_to_unit
result[is.na(pts)] <- m
This fixes the issue and does not seem to break any other behaviour. This is a pretty minor fix. Hope it can get merged!
The text was updated successfully, but these errors were encountered:
Some more context:
This is the error I was getting on Neovim after configuring the LSP.
I modified the neovim source code to expose the exact comparison that was causing the error. See that is tries to compare a string with a number.
After exposing the variable is was a string containing NA. This is pretty common R stuff to from there I tried to make my fix.
NA
Sorry, something went wrong.
Related: #481
Successfully merging a pull request may close this issue.
The language server introduces NA when code like the following occurs
This causes for the Neovim lsp interface to error out. In this like shiny this is a very common thing to find.
My fix was pretty easy, I went to the
code_point_to_unit
function and added the following:This fixes the issue and does not seem to break any other behaviour. This is a pretty minor fix. Hope it can get merged!
The text was updated successfully, but these errors were encountered: