Noticed that although the API spec stopped tagging the non-nullable properties as nullable, it still didn't make them required.
There is no built-in way to do this so I borrowed someone's code.
With this, any non-nullable property will be automatically required.
(here "required" means the JSON object will always contain the property)
Noticed that although the API spec stopped tagging the non-nullable properties as nullable, it still didn't make them required. There is no built-in way to do this so I borrowed someone's code.
With this, any non-nullable property will be automatically required.
(here "required" means the JSON object will always contain the property)