URL path extension APIs should strip trailing slashes #965
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.
When supplying a directory to
URL
likeURL(filePath: "/my/directory", directoryHint: .checkFileSystem)
, the initializer will automatically append a trailing slash, so the.path()
is/my/directory/
.The current logic for
.appendingPathExtension("zip")
then directly appends the path extension, creating the unexpected path:/my/directory/.zip
. A similar issue occurs where.deletingPathExtension()
does not search before the trailing slash.This PR restores the behavior from before the Swift
URL
implementation, which strips the trailing slash before appending or deleting the path extension, then appends a slash if the path was a directory. E.g. after appending the path extension, the resulting.path()
is now/my/directory.zip/
as expected.