Rebilly/api-definitions

fix nullable usage

adamaltman opened this issue · 0 comments

A true value adds "null" to the allowed type specified by the type keyword, only if type is explicitly defined within the same Schema Object. Other Schema Object constraints retain their defined behavior, and therefore may disallow the use of null as a value. A false value leaves the specified or default type unmodified. The default value is false.

We tend to use nullable with allOf and not on a typed Schema Object.

nullable: true
allOf:
  - $ref: ./foo.yaml

This is incorrect.