As discussed at [1], "subtypes can add restrictions, but they cannot
relax restrictions that are already in place." These fields need to be
marked nullable and then "subclassed" to set non-nullability if
required.
[1] https://github.com/OAI/OpenAPI-Specification/issues/1368
Signed-off-by: Stephen Finucane <stephen@that.guru>
type: object
title: Owner
readOnly: true
+ nullable: false
allOf:
- $ref: '#/components/schemas/UserEmbedded'
patches:
readOnly: true
UserEmbedded:
type: object
+ nullable: true
properties:
id:
title: ID
type: object
title: Owner
readOnly: true
+ nullable: false
allOf:
- $ref: '#/components/schemas/UserEmbedded'
patches:
readOnly: true
UserEmbedded:
type: object
+ nullable: true
properties:
id:
title: ID
type: object
title: Owner
readOnly: true
+ nullable: false
allOf:
- $ref: '#/components/schemas/UserEmbedded'
patches:
readOnly: true
UserEmbedded:
type: object
+ nullable: true
properties:
id:
title: ID
type: object
title: Owner
readOnly: true
+ nullable: false
allOf:
- $ref: '#/components/schemas/UserEmbedded'
patches:
readOnly: true
UserEmbedded:
type: object
+ nullable: true
properties:
id:
title: ID
type: object
title: Owner
readOnly: true
+ nullable: false
allOf:
- $ref: '#/components/schemas/UserEmbedded'
patches:
readOnly: true
UserEmbedded:
type: object
+ nullable: true
properties:
id:
title: ID