Unable to set default value to null

[ibm]

Unable to set default value to null

[dpopp07]

Glad you are enjoying this tool! Looking at the spec, you are indeed correct and we should support that use case. I will look into it soon. Thanks for reporting!

[mkistler]

I think simply omitting default is equivalent to default: null. Is there some reason this isn't sufficient?

[gamezfreak]

@mkistler I tried removing the default: null parameter but that also causes "default: null" to be removed from the documentation I am generating with redoc. I'd prefer that to be explicit in my documentation that it will be null and not an empty string when unspecified. Maybe that is an issue there as well in their project, but I think the OAS 3.0.3 clarification on nullable would still allow default: null. I'm trying to use null vs "" to be forward-thinking around data migrations; did the user set an empty value vs never set any value.

[sirosen]

To offer another motivating use-case for this: I'm generating an openapi spec from my schemas, and default: null is the output from my spec generation tool. So even if I wanted to remove default: null, it's difficult to do so in this case.

It would be nice to be able to disable this check altogether as a workaround, but I don't think that's supported by the config options.

[dpopp07]

🎉 This issue has been resolved in version 0.33.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀