-
Notifications
You must be signed in to change notification settings - Fork 26
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
Make IntelliSense work in unsaved files #34
Comments
Solargraph usually works on untitled files as long as it knows the language mode, e.g., if you set it to Ruby with the |
Yes, I played around with SolarGraph a bit earlier, and here's what I recall: Open a new VSC window. Open a new file (don't save it). Set language to Ruby (of course, I always did this when testing SolarGraph). IntelliSense doesn't work here. However if I open a saved Ruby file first, then open a new document, then IntelliSense works fine there. Although for some reason, it still sometimes fails to work here. This isn't an edge case in my opinion. I definitely frequently open a new window in VSC, then open a new document and hack away at some Ruby code. Any rough ETA on the language server protocol version, if you don't mind? |
Thanks for the information. I'll work on this bug for an upcoming release. I hope to release the LSP version by the end of this month, or possibly the first week of April. |
There appears to be a limitation (or a bug) in either VSCode or the language client that prevents them from updating the language server when you change an unsaved file's language mode. I'll keep looking for a workaround. |
Right now, SolarGraph only works in unsaved files. But I'd like it if it also worked in unsaved files.
I've attached two GIFs if necessary.
Unsaved file, where extension doesn't work:
Saved file, where extension works:
The text was updated successfully, but these errors were encountered: