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

Store URIs in entries instead of file paths #2926

Merged
merged 1 commit into from
Nov 28, 2024

Conversation

vinistock
Copy link
Member

@vinistock vinistock commented Nov 27, 2024

Motivation

Another step towards #1908

Entries need to store URIs instead of file paths. Otherwise, we cannot represent an unsaved file (since there's no file path associated to it, only a URI).

Implementation

This PR changes entries to store URIs, but still maintains the assumption that every entry is backed by a file path on disk. This allows us to minimize the number of changes for this PR.

Once this goes in, then we can start looking into indexing unsaved files, which use the untitled scheme instead of file and then we will need to handle the possibility of the file path being nil.

@vinistock vinistock added server This pull request should be included in the server gem's release notes other Changes that aren't bugfixes, enhancements or breaking changes labels Nov 27, 2024 — with Graphite App
Copy link
Member Author

vinistock commented Nov 27, 2024

@vinistock vinistock marked this pull request as ready for review November 27, 2024 22:03
@vinistock vinistock requested a review from a team as a code owner November 27, 2024 22:03
@vinistock vinistock merged commit 6172ba4 into main Nov 28, 2024
39 checks passed
@vinistock vinistock deleted the 11-27-store_uris_in_entries_instead_of_file_paths branch November 28, 2024 13:55
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