Skip to content

Follow standard REST-JSON content-type handling #2845

New issue

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

Merged
merged 8 commits into from
Nov 15, 2021

Conversation

dagnir
Copy link
Contributor

@dagnir dagnir commented Nov 15, 2021

Motivation and Context

Standardize REST-JSON behavior across SDKs.

Description

Update the REST-JSON marshalling logic to conform to the standard expected behavior WRT to the Content-Type of the request.

Testing

  • New protocol tests
  • mvn clean install
  • Running integ tests

Screenshots (if appropriate)

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)

Checklist

  • I have read the CONTRIBUTING document
  • Local run of mvn install succeeds
  • My code follows the code style of this project
  • My change requires a change to the Javadoc documentation
  • I have updated the Javadoc documentation accordingly
  • I have read the README document
  • I have added tests to cover my changes
  • All new and existing tests passed
  • A short description of the change has been added to the CHANGELOG
  • My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

  • I confirm that this pull request can be released under the Apache 2 license

dagnir and others added 7 commits October 7, 2021 10:21
Add SDK standard test cases that verify correct conte-type handling for the
REST-JSON protocol.
* Follow standard REST-JSON content-type handling

Update the REST-JSON marshalling logic to conform to the standard expected
behavior WRT to the `Content-Type` of the request.

* Add additional protocol test

Verifies that when there are unbound members (no `location` trait), and they are
null, that we continue to marshall to an empty JSON object in the body.

* Extract block to method
This fixes an edge case in the REST-JSON marshaller: if the request has neither
an explicit payload nor implicit payload members (i.e. members not explicitly
bound to an location), then the marshaller should not create an create an
object. i.e. the request body should be "", and not "{}".
Correctly propagate the existence of implicit event members down to the
marshaller.
@dagnir dagnir requested a review from a team as a code owner November 15, 2021 16:26
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 1 Code Smell

94.9% 94.9% Coverage
0.0% 0.0% Duplication

@dagnir dagnir merged commit 5825618 into master Nov 15, 2021
aws-sdk-java-automation added a commit that referenced this pull request Dec 27, 2023
…0f2d4b5e4

Pull request: release <- staging/2273ef8b-924d-4c51-8c61-c610f2d4b5e4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants