openapi: 3.0.3
info:
title: Simple API
version: 1.0.0
paths:
/:
post:
summary: Simple POST endpoint
requestBody:
content:
application/json:
schema:
type: object
required:
- field
properties:
field:
type: string
application/merge-patch+json:
schema:
type: object
required:
- different
properties:
different:
type: string
responses:
'200':
description: A simple string response
content:
application/json:
schema:
type: object
required:
- field
properties:
field:
type: string
application/merge-patch+json:
schema:
type: object
required:
- different
properties:
different:
type: string
...having multiple response media types within the same status code, if the example has Content-Type headers in request and response, they should be matched and loaded in the scenarios for the specific request-response media type combination.
How:
Modified OperationIdentifier to hold the request and response Content-Type header values from the example
Modified Scenario to use these when selecting the relevant examples
What:
Given a spec like the following:
...having multiple response media types within the same status code, if the example has Content-Type headers in request and response, they should be matched and loaded in the scenarios for the specific request-response media type combination.
How:
Checklist: