Allow more than one parameter per URL segment. #47
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
|
Aces. Thanks @bennor! |
anaisbetts
pushed a commit
that referenced
this pull request
Jun 30, 2014
Allow more than one parameter per URL segment.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This change adds support for multiple parameters per URL segment.
Not sure if it goes against any RFC standards or anything, but a while back I made the (questionable?) decision to express image sizes in my app's API as
"/{id}/{width}x{height}". Works fine with Web API, but Refit doesn't like it. 💣I'm working around this in my app's client at the moment with a custom
Resolutiontype with a.ToString()that serializes it to"{width}x{height}", so if you're not keen on allowing multiple parameters in a segment I'm happy for you to just 🔪 this PR.