Empty default in schema is parsed as null

Parser version:

2.0.2

Description:

OAS 3 spec (partial):

components:
  parameters:
    example:
      name: example
      description: example
      in: query
      required: false
      schema:
        type: array
        items:
          type: string
        default: ''

The parameter schema parser treats empty strings as null.

schema.getDefault() returns null.

The following results in a proper default value being set:

components:
  parameters:
    example:
      name: example
      description: example
      in: query
      required: false
      schema:
        type: array
        items:
          type: string
        default: 'a,b,c'

schema.getDefault() returns "a,b,c".

[webron]

That’s where it gets complicated. Not sure there is a way to do it, as it’s an edge case.

Theoretically, you could set the default value to [] which is indeed an empty JSON array. However, the value of the array in this case is not a JSON, especially with the defaults for query parameters having style: form, explode: true by default - suggesting there’s no real way of representing that. I’d recommend filing a ticket on the spec asking that question. We may simply agree that a JSON array value would be representative of such values regardless of how those are being converted to the request.

That said, in your specific example, one might argue that there’s no point providing a default value of an empty array as it most likely does not affect the documentation nor implementation.

[gracekarina]

Hi, the scope of the issue changed, the validation of this new scope made in another PR. Thanks @jason-cohen for reporting this and sorry for the long reply. I will close this because is no longer an issue.