[Apex] better handling of different content-type in the response #7515
Conversation
This file contains 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
|
@henryh-force thanks for the PR |
muenzpraeger
approved these changes
Sep 27, 2020
|
Pushed 085b230 to fix the CI failure. Let's see how that goes. |
wing328
changed the title
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.
openapi-generator/modules/openapi-generator/src/main/resources/apex/OAS.cls
If you send a response that contains anything in addition to "application/json" nothing is returned.
Set the toReturnValue to validate for more than just application/json e.g. UTF-8 within the Content Type.
To fix #7500