chore(must-have-content-type): Remove rule #38
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
…'t be valid without a content type for the response This rule is not neccessary as having a content type is neccessary for the openapi spec to be considered valid anyways. It provides no real benefit while only possibly causing bugs.
markbrockhoff
force-pushed
the
remove-rule-must-have-content-type
branch
from
47b5599
to
e0b30ad
Compare
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.
Remove rule as the openapi spec wouldn't be valid without a content type for the response
This rule is not neccessary as having a content type is neccessary for the openapi spec to be considered valid anyways. It provides no real benefit while only possibly causing bugs.