Fix API clients ignoring resolved endpoint's URL Path and RawQuery #1199
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
This was referenced Mar 30, 2021
jasdel
force-pushed
the
jasdel/fixup/LosslessPathAndQuery
branch
from
3d234f5 to
261f021
Compare
skmcgrail
approved these changes
Mar 30, 2021
skotambkar
approved these changes
Mar 31, 2021
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.
Fixes the API clients to not ignore the resolved endpoint's URL Path and RawQuery parameters. Instead of ignoring the values the SDK will append the operation's modeled Path and Query String.
Fixes #1191
Depends on aws/smithy-go#280