Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

New Test Case to Ensure PATCH Responses Are Correct #45

Open
mraineri opened this issue Aug 11, 2022 · 1 comment
Open

New Test Case to Ensure PATCH Responses Are Correct #45

mraineri opened this issue Aug 11, 2022 · 1 comment
Labels
cleanup Used for issues that are stale and should be considered for closing enhancement New feature or request

Comments

@mraineri
Copy link
Contributor

There are some services that respond with 200 OK to PATCH requests, but their response body is either an error response with messages indicating "success", or simply the extended info messages arrays also indicating "success". Per the spec, 200 OK is supposed to contain the modified resource in response to a PATCH; the extended info array could be in there to convey warnings or properties that could not be modified, but that's an optional addition to the response.
@mraineri mraineri added enhancement New feature or request cleanup Used for issues that are stale and should be considered for closing labels Jun 26, 2024
@mraineri
Copy link
Contributor Author

May be covered already with the test_patch_mixed_props test... Needs to be tested a bit...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cleanup Used for issues that are stale and should be considered for closing enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mraineri