URL(filePath:) should not treat "~" as absolute #961
Merged
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.
Paths beginning with
~
should not be treated as absolute forURL(filePath:)
. This is because when constructing aURLComponents
for a file path we consider absolute, we do:This would create the string like
file://~/
. However,URLComponents
rejects this string because the~
is ambiguous--it looks like a host. This can leadcomponents.url!
to crash when force-unwrapping.This PR changes the
isAbsolute
check to only consider/
paths absolute. If the path starts with~
, we will try to expand the tilde, then ensure that the result is absolute.