We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The following comment was left in the code: // TODO fix the edge case: a shape which is an operational input (i.e. has members bound to HTTP semantics) could be re-used elsewhere not as an operation input which means everything is in the body
Related issue: #710
fun Shape.isInHttpBody() checks to see if a shape is in the body of the http request. This should work for any valid shape with bound members.
fun Shape.isInHttpBody()
The TODO comment suggests that the code logic does not work properly when an input to operation is re-used elsewhere not as an input to an operation.
This issue includes the work to re-produce this edge case which can likely be accomplished by creating a smithy file and corresponding test.
No response
to be confirmed
The text was updated successfully, but these errors were encountered:
Moved to 2143
Sorry, something went wrong.
No branches or pull requests
Describe the bug
The following comment was left in the code:
// TODO fix the edge case: a shape which is an operational input (i.e. has members bound to HTTP semantics) could be re-used elsewhere not as an operation input which means everything is in the body
Related issue: #710
Expected Behavior
fun Shape.isInHttpBody()
checks to see if a shape is in the body of the http request. This should work for any valid shape with bound members.Current Behavior
The TODO comment suggests that the code logic does not work properly when an input to operation is re-used elsewhere not as an input to an operation.
Reproduction Steps
This issue includes the work to re-produce this edge case which can likely be accomplished by creating a smithy file and corresponding test.
Possible Solution
No response
Additional Information/Context
No response
AWS SWIFT SDK version used
to be confirmed
Compiler and Version used
to be confirmed
Operating System and version
to be confirmed
The text was updated successfully, but these errors were encountered: