Merge pull request #1674 from RepreZen/v3.0.2-dev-discriminator-pet_type

Ron · web-flow · commit 1bdda2f81746 · 2018-10-03T14:08:52.000-06:00
Consistent use of property name in schema examples: `petType` vs `pet_type`
diff --git a/versions/3.0.2.md b/versions/3.0.2.md
@@ -2708,15 +2708,15 @@ MyResponseType:
   - $ref: '#/components/schemas/Dog'
   - $ref: '#/components/schemas/Lizard'
   discriminator:
-    propertyName: pet_type
+    propertyName: petType
 ```
 
-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:
+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:
 
 ```json
 {
   "id": 12345,
-  "pet_type": "Cat"
+  "petType": "Cat"
 }
 ```
 
@@ -2732,7 +2732,7 @@ MyResponseType:
   - $ref: '#/components/schemas/Lizard'
   - $ref: 'https://gigantic-server.com/schemas/Monster/schema.json'
   discriminator:
-    propertyName: pet_type
+    propertyName: petType
     mapping:
       dog: '#/components/schemas/Dog'
       monster: 'https://gigantic-server.com/schemas/Monster/schema.json'
@@ -2752,12 +2752,12 @@ components:
     Pet:
       type: object
       required:
-      - pet_type
+      - petType
       properties:
-        pet_type:
+        petType:
           type: string
       discriminator:
-        propertyName: pet_type
+        propertyName: petType
         mapping:
           dog: Dog
     Cat:
@@ -2790,7 +2790,7 @@ a payload like this:
 
 ```json
 {
-  "pet_type": "Cat",
+  "petType": "Cat",
   "name": "misty"
 }
 ```
@@ -2799,7 +2799,7 @@ will indicate that the `Cat` schema be used.  Likewise this schema:
 
 ```json
 {
-  "pet_type": "dog",
+  "petType": "dog",
   "bark": "soft"
 }
 ```
