Skip to content
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

Merged

Conversation

vinistock
Copy link
Member

@vinistock vinistock commented Nov 27, 2024

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.

Copy link
Member Author

vinistock commented Nov 27, 2024

@vinistock vinistock added other Changes that aren't bugfixes, enhancements or breaking changes server This pull request should be included in the server gem's release notes labels Nov 27, 2024 — with Graphite App
@vinistock vinistock marked this pull request as ready for review November 27, 2024 22:04
@vinistock vinistock requested a review from a team as a code owner November 27, 2024 22:04
Copy link
Contributor

@andyw8 andyw8 left a 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.

@vinistock vinistock changed the base branch from 11-27-store_uris_in_entries_instead_of_file_paths to graphite-base/2927 November 28, 2024 13:55
@vinistock vinistock force-pushed the 11-27-use_entry_uri_where_possible_instead_of_file_path branch from dca4475 to 1135b23 Compare November 28, 2024 13:55
@vinistock vinistock changed the base branch from graphite-base/2927 to main November 28, 2024 13:55
@vinistock vinistock force-pushed the 11-27-use_entry_uri_where_possible_instead_of_file_path branch from 1135b23 to 8d6bf75 Compare November 28, 2024 13:55
Copy link
Member Author

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.

Copy link
Member Author

Merge activity

  • Nov 28, 9:23 AM EST: Graphite couldn't merge this PR because it failed for an unknown reason.

@vinistock vinistock merged commit ce50f49 into main Nov 28, 2024
35 checks passed
@vinistock vinistock deleted the 11-27-use_entry_uri_where_possible_instead_of_file_path branch November 28, 2024 14:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
other Changes that aren't bugfixes, enhancements or breaking changes server This pull request should be included in the server gem's release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants