fix: Let Representations always have a body #987
Merged
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.
Closes #982 and indirectly closes #969 (since we now accept empty/missing bodies).
Operation.body
is no longer optional.Representation
has a newisEmpty
parameter, which in practice is a shortcut for checking if there is a content-type.I looked into having the
data
field of a Representation be optional, but the problem is that classes then no longer can be sure they get a data stream from functions that return a Representation. It would also potentially cause confusion between an empty data stream and an undefined one.