Skip to content

New Test Case to Ensure PATCH Responses Are Correct #45

@mraineri

Description

@mraineri

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    cleanupUsed for issues that are stale and should be considered for closingenhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions