response-property-discriminator-mapping-changed
Response property discriminator mapping changed.
Not breaking (level: info)
oasdiff records this in the changelog but does not fail CI by default. Clients that worked under the old contract still work, so existing clients are not affected.
What this check detects
The response-side counterpart of a request discriminator mapping change: a value of the discriminator property now points at a different schema.
It is informational for the same reason, the mapping guides which subschema tooling resolves to, not what the server may return. Still worth a look, because a generated client deserializes the response into whatever model the mapping names.
Example
A response carrying "petType": "cat" now resolves to Dog for tooling that follows the mapping.
Change its severity
oasdiff reports response-property-discriminator-mapping-changed as informational, so it does not fail CI. To treat it as a warning or an error under your own compatibility policy, or to turn it off, set its level in a severity-levels file:
Put one rule per line; the level can be err, warn, or info, or none to disable the check entirely:
# severity.txt
response-property-discriminator-mapping-changed errThen pass it to oasdiff:
oasdiff changelog base.yaml revision.yaml --severity-levels severity.txt