Fix empty response tables #3271
Merged
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
…docs say it does.
this commit changes the table to reflect that.
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.
Two intermingled issues.
The delete operations against our API do not return JSON. We say that in the docs (see https://fusionauth.io/docs/apis/emails#response-4 ) where it states
This API does not return a JSON response body.. But the table underneath it contradicts:The request was successful. The response will contain a JSON body.This PR fixes the delete common component to remove the second sentence of the success code table.
There are a few POST operations that don't return JSON. They are subject to the same contradictions as the delete method above. I fixed those.