-
Notifications
You must be signed in to change notification settings - Fork 172
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
Use Entry#uri where possible instead of file path #2927
Use Entry#uri where possible instead of file path #2927
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
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 wonder if the language-server gem maintainers would consider a PR to allow us to pass URIs instances as well as strings, since we do it so frequently.
62c7083
to
6172ba4
Compare
dca4475
to
1135b23
Compare
1135b23
to
8d6bf75
Compare
I think they'd be open to it. I had a chance to meet the maintainer at RubyKaigi. There are many things we could upstream there, like all of the foundational parts of writing the language server and dealing with queues, workers, sending requests, expecting responses and so on. We just never had the time because there's always so many other higher priority items. |
Merge activity
|
Motivation
Another step towards #1908
This PR starts using the entry's URI directly instead of rebuilding them from the file paths. This allows us to do less work, but is also an important step so that features will actually work once we index unsaved files.
Implementation
Started using the entry's URI for building responses, like definition locations.