feature/nullable

[MertcanDinler]

Support for nullable values for OpenApiSpecs.
If the parameter is not required, if it is specified to be nullable with the BodyParam attribute, or if there is a nullable rule in the validation, this field will be added to the OpenApiSpecs as nullable.

[shalvah]

I need to think about this a bit. I see the distinction, but I'm always skeptical about adding OpenAPI-only features. I daresay, for most devs in a dynamically-typed language like PHP, a required parameter is functionally equivalent to non-null (in most cases).

[liverocaisson]

@MertcanDinler cc @shalvah
I tried also to implement a similar nullable fonctionnality when not required -> nullable : true
but tests don't pass. If someone can help.
#739

[jfoliveira]

@MertcanDinler cc @shalvah I tried also to implement a similar nullable fonctionnality when not required -> nullable : true but tests don't pass. If someone can help. #739

@liverocaisson added more suggestions to #739
Please have a look when you have a chance.

[shalvah]

Been busy, will take a look at these sometime this week or next.

[shalvah]

Hey, sorry I didn't get back to this! I think I'll accept it. Note that, as you've PRed, this feature only works with the attribute and the validation rule, and only affects the OpenAPI output. This means:

1. It doesn't work with the annotations (@bodyParam, ...)
2. It doesn't change the HTML page output.

I think I'd like to change the second, but the first will probably stay as is for a while. In the meantime, I'll accept this, but label it "experimental". Thanks for your contribution!