Add support for exploded GET parameters #1065
Open
Conversation
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
|
jjjasper
force-pushed
the
support-for-exploded-params
branch
from
4cc5a63 to
58b0ecb
Compare
|
Please add this to the change log (and mention it only works for swift) |
jjjasper
force-pushed
the
support-for-exploded-params
branch
from
58b0ecb to
03da839
Compare
|
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.
This pull request adds support for exploded GET parameters, based on OpenAPI specification.
param=1¶m=2¶m=3
param=1,2,3
In all other cases current functionality is maintained.
There is a PR on backbase-client-common-ios to add support for this feature.