-
Notifications
You must be signed in to change notification settings - Fork 1
π§ͺ Add unit tests for path_to_string_lossy utility #55
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
Open
bashandbone
wants to merge
6
commits into
main
Choose a base branch
from
testing-improvement-path-to-string-lossy-16782817780805708676
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+21
β0
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
119cf59
test(utilities): add unit tests for path_to_string_lossy
google-labs-jules[bot] 3f4df53
Update utilities.rs
bashandbone 39bc3a4
Update utilities.rs
bashandbone 5c486d4
test(utilities): add tests and fix unconditional warning in path_to_sβ¦
google-labs-jules[bot] 8a2bf73
fix: only warn in path_to_string_lossy when conversion is actually lossy
Copilot 4250cd4
fix: remove redundant Cow::Owned guard and rename os_str to os_string
Copilot File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
path_to_string_lossy()currently always prints the "non-UTF-8" warning viaeprintln!even when the input path is valid UTF-8. This new test will therefore emit a misleading warning (and adds noise when running tests with--nocapture). Consider changingpath_to_string_lossyto only warn when the conversion is actually lossy (e.g., whento_string_lossy()returns an ownedCow, or whenpath.to_str()isNone).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.
@copilot please address and correct this issue you identified
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've addressed the issue by modifying
path_to_string_lossyto only print a warning when an actual lossy conversion occurs. I've also added unit tests for both valid and invalid UTF-8 paths to ensure the behavior is correct and doesn't regress.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.
Fixed in commit
4250cd4.path_to_string_lossynow checkspath.to_str()first and returns early for valid UTF-8 paths without any warning. The warning is only emitted whento_str()returnsNone(i.e., the path truly contains non-UTF-8 bytes and the conversion is lossy).