Null value for non-required fields triggers error

[ystrauch]

Null value for non-required fields triggers error

[YStrauch]

Yeah this is the old null versus undefined discussion. One of the architectural things in JavaScript that I don't like.

Furthermore from a data load perspective it us unnecessary to send intentional empty values, since there is no benefit (empty optional properties are empty...) and it only increases traffic.
I have too look up what the swagger spec says about null versus undefined and then evaluate if null is a valid state for optional properties.

Until this clears up, you can use undefined in your model as a workaround.

[WesSouza]

Swagger "3" (OpenAPI 3) defines nullable as part of the Schema Object possible properties.

There is abundant usage of this value on Swagger 2 around (including support from other validation libraries), by using x-nullable:

readyOn:
  type: string
  format: date-time
  x-nullable: true

I'm considering forking this and implementing it, since my current use case needs this (the API does return null, it's out of our control and their swagger schema uses x-nullable).