You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 30, 2022. It is now read-only.
Consistent use of property name schema examples: petType vs pet_type
* Pet Schema in the MediaTypes Examples and Schema Object Examples uses the camelCase notation(petType),
* While Pets from the Discriminator Object use snake_case (pet_type).
It's inconsistent.
I chose the camelCase notation because it's used for propertyNames by the OpenAPI specification itself.
Copy file name to clipboardExpand all lines: versions/3.0.2.md
+9-9Lines changed: 9 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -2707,15 +2707,15 @@ MyResponseType:
2707
2707
- $ref: '#/components/schemas/Dog'
2708
2708
- $ref: '#/components/schemas/Lizard'
2709
2709
discriminator:
2710
-
propertyName: pet_type
2710
+
propertyName: petType
2711
2711
```
2712
2712
2713
-
The expectation now is that a property with name `pet_type` _MUST_ be present in the response payload, and the value will correspond to the name of a schema defined in the OAS document. Thus the response payload:
2713
+
The expectation now is that a property with name `petType` _MUST_ be present in the response payload, and the value will correspond to the name of a schema defined in the OAS document. Thus the response payload:
0 commit comments