fix: detect tree output filenames as file links#10004
fix: detect tree output filenames as file links#10004princepal9120 wants to merge 2 commits intowarpdotdev:masterfrom
Conversation
|
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Prince Pal.
|
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
There was a problem hiding this comment.
Overview
This PR extends file-link separator handling to common tree-output box-drawing glyphs and adds regression tests for tree-style path candidates.
Concerns
- The added tree-output tests use whitespace before the filename, so they do not prove the new box-drawing separators are required; the existing space separator already isolates the filename.
Verdict
Found: 0 critical, 1 important, 0 suggestions
Request changes
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
e6f9105 to
6515123
Compare
|
/oz-review |
|
I'm re-reviewing this pull request in response to a review request. You can view the conversation on Warp. I reviewed this pull request and requested human review from: @warpdotdev/oss-maintainers. Comment Powered by Oz |
Oz no longer requests changes for this pull request after the latest automated review.
There was a problem hiding this comment.
Overview
This expands file-link separator handling to include common tree-style box-drawing glyphs and adds candidate-generation coverage for tree output, including multibyte filenames and absolute path leaves.
Concerns
- No blocking correctness, security, or performance concerns found in the changed lines.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
|
@princepal9120 you'll need to modify your commit so the author information matches your github account, and then sign our CLA - this is a requirement for us to accept contributions. you can use the following to do so: where [email protected] is an email address associated with your GitHub account. |
Done |
|
looks like some of the tests you added are failing, can you fix? the issue is a char/byte index mismatch issue - looks like you're trying to index using character indices, but rust's string indexing uses byte indices. |
| #[cfg_attr(not(feature = "local_fs"), allow(dead_code))] | ||
| #[derive(Clone, Copy)] | ||
| struct SeparatorByteRange { | ||
| start: usize, | ||
| end: usize, | ||
| } |
There was a problem hiding this comment.
we already have a string_offset::ByteOffset wrapper type that we've created specifically for semantically clarifying byte vs. char offsets like this - thoughts on using Range<ByteOffset> instead of the custom type?
Summary
Fixes #9909
Testing
cargo: command not found).