Skip to content

bug: Loosen file path requirement for discover command#31

Merged
ethowitz merged 1 commit intomainfrom
be-more-lenient-with-file-paths-discover
Oct 14, 2025
Merged

bug: Loosen file path requirement for discover command#31
ethowitz merged 1 commit intomainfrom
be-more-lenient-with-file-paths-discover

Conversation

@ethowitz
Copy link
Owner

Previously, we were expecting the path passed to DiscoverArgument::Path
to be path to a file that already exists. However, it's possible that
rust-analyzer will invoke us with a path to a not-yet-existing file if
the user has opened a new file in their editor but hasn't yet saved.
This commit removes the requirement that this path point to a file on
disk to improve UX in this situation.

Previously, we were expecting the path passed to `DiscoverArgument::Path`
to be path to a file that already exists. However, it's possible that
rust-analyzer will invoke us with a path to a not-yet-existing file if
the user has opened a new file in their editor but hasn't yet saved.
This commit removes the requirement that this path point to a file on
disk to improve UX in this situation.
@ethowitz ethowitz merged commit ce0bd7c into main Oct 14, 2025
7 checks passed
@ethowitz ethowitz deleted the be-more-lenient-with-file-paths-discover branch October 14, 2025 13:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant