Skip to content

Commit 1823463

Browse files
authored
Merge pull request #3728 from handrews/disc-strings
Non-string discriminator values have undefined behavior (3.0.4)
2 parents 761f50f + cb0e8c6 commit 1823463

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

versions/3.0.4.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2719,7 +2719,7 @@ Field Name | Type | Description
27192719
<a name="propertyName"></a>propertyName | `string` | **REQUIRED**. The name of the property in the payload that will hold the discriminator value.
27202720
<a name="discriminatorMapping"></a> mapping | Map[`string`, `string`] | An object to hold mappings between payload values and schema names or references.
27212721

2722-
The discriminator object is legal only when using one of the composite keywords `oneOf`, `anyOf`, `allOf`.
2722+
The discriminator object is legal only when using one of the composite keywords `oneOf`, `anyOf`, `allOf`. Note that because the discriminating property's value is used as a component name and/or as the key in the `mapping` object, the behavior of any value that is not a string is undefined.
27232723

27242724
In OAS 3.0, a response payload MAY be described to be exactly one of any number of types:
27252725

0 commit comments

Comments
 (0)