feat(smithy-client): stricter parsing of request/response bodies #2713
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.
Description
Structured, non-payload-bound requests (to servers) and responses (to clients) should always be a JSON object in the REST/JSON protocol. This adds parsing utility functions so we can update the generator to assert that these requests/responses are JSON objects that are not null.
Testing
I have a local change to the generator, and I regenerated all clients and client and server protocol tests, and ran the protocol tests. They passed.
Additional context
I will have a PR to update the generator, and to update the generated code, after this.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.