request-body-enum-value-removed

Request body enum value deleted.

directionrequestareaschemakindvaluesactionremove

Not breaking (level: info)

oasdiff reports this in the changelog but does not treat it as a breaking change, so it does not fail CI by default.

Example

Before
requestBody:
  content:
    application/json:
      schema:
        type: string
        enum: [visa, mastercard, amex]
After
requestBody:
  content:
    application/json:
      schema:
        type: string
        enum: [visa, mastercard]

The request body no longer accepts "amex". Clients that still send it will be rejected.

Change its severity or ignore it

To change the severity oasdiff assigns to request-body-enum-value-removed, list its id and a level in a severity-levels file, one rule per line. The level can be err, warn, or info, or none to disable the check entirely:

# severity.txt
request-body-enum-value-removed err

Then pass it to oasdiff:

oasdiff changelog base.yaml revision.yaml --severity-levels severity.txt

Setting the level to none disables the check, so it is no longer reported at all.

Related schema rules

Browse all 500 checks →