Work around empty query components bug. #86
Merged
Conversation
This file contains 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
mbrandonw
commented
Dec 4, 2017
| ( | ||
| data.path.isEmpty && data.query.isEmpty | ||
| ? (base ?? URL(string: "/")) | ||
| : urlComponents(from: data).url(relativeTo: base) |
There was a problem hiding this comment.
this was coming back nil on linux, so we have to first check if path+query are empty, and if so just default to the base url.
mbrandonw
commented
Dec 4, 2017
| @@ -4,6 +4,7 @@ import Either | |||
| import Prelude | |||
|
|
|||
| enum Routes { | |||
| case home | |||
There was a problem hiding this comment.
we weren't seeing this bug in the tests cause the root route technically when to the url /home. I've now create a separate home route so that we can test both and fully root URL and something with path components.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I just filed this bug https://bugs.swift.org/browse/SR-6405 and this PR works around it.