feat: add --x-nullable-as-nullable to treat schemas with x-nullable as being able to specify null

[mitchell-merry]

Changes

Essentially adds the nullable feature from 3.0 into 2.0 as well, behind the --x-nullable-as-nullable flag.

How to Review

Stacked on #1575!

Checklist

• Unit tests updated
  Specifically didn't add too much so as not to over-test. This is not a commonly used version, anywho

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9fa2708

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[drwpow]

Thanks for adding this! I’m good with this addition. While I know 3.x encourages type: [null] as the recommended way, nullable: true and x-nullable: true are still really common patterns I see in 3.x schemas and I think supporting both doesn’t stand in the way of the 3.x specs while providing value to users. +1 to this landing.

[mitchell-merry]

Specifically, this is to support a 2.x schema, where I believe there is no official pattern for nullable (outside of this x-nullable thing) which is why I am PRing into 5.x 😄.

Thanks for the quick reviews, though!

[mitchell-merry]

Thanks for the merge! Could we get a release of 5.x with this change?

[drwpow]

Published!