Open davidhjones opened 6 years ago
I see the implementation. Seems like the current strategy is an opt-in approach, where 204 / no content returned is the default (if no header is provided). This seems counter-intuitive, but if I understand correctly, changing to an opt-out approach (return 200 and entity) by default would be a breaking change? If there is not intention of changing the strategy to "fix" this issue, then it can be closed.
By default, UpdatedODataResult is returning an http status of 204. It should return 200 by default and 204 if requested.
Assemblies affected
OData WebApi lib 7.3.1
Reproduce steps
Expected result
HttpStatus of 200 is returned with the body consisting of the updated entity.
Actual result
HttpStatus of 204 is returned with an empty body
Additional detail
Should operate exactly like CreatedODataResults, except rather than 201 default, should be a 200 default for updated entity.