OpenAPI3 output does not handle nullable values correctly

[reieRMeister]

Nominal

Rendering an API Blueprint document to OpenAPI3 with flag --open-api-3 converts an input property like this:

    + errors (required, array, nullable)

into this:

  errors:
    type: array
    nullable: true
    items: {}

Actual

Rendering an API Blueprint document to OpenAPI3 with flag --open-api-3 converts an input property like this:

    + errors (required, array, nullable)

into this:

  errors:
    type:
      - array
      - 'null'
    items: {}

Remarks

According to the OpenAPI spec »null is not supported as a type« and instead the nullable property must be used.

[kminami]

Thank you for reporting!
I have fixed this at v1.14.1.
Please confirm.

[reieRMeister]

Looks good to me. 👍

[kminami]

Thanks!