Skip to content

Transaction Ext validation should handle multiple response status code options and content types #343

@philvarner

Description

@philvarner

Transaction Extension validation currently assumes the responses will be 201 and 202, but these can be other status codes. The content type for those is not defined in the Transaction Extension, but it should be, and then those should be validated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions