Add OpenAPI 3.1 Support

[darrelmiller]

Includes:

• Add webhooks property to the root document #1046
• Adds a summary property in the info object #1039
• Add license SPDX identifier #1042
• Add reusable path items to components object #1056
• Add summary and description to OpenApiReference object #1077
• Add root property jsonSchemaDialect #1138
• Support the core and validation keywords from the latest JSON schema specification (JSON Schema Specification Draft 2020-12) #1275
• Add support for $schema, $id, $comment, $vocabulary, $dynamicRef, $dynamicAnchor, $recursiveAnchor, $recursiveRef #1274
• Map nullable to null type #1273
• Enable upcasting from V2/V3 to 3.1 #1272
• ExclusiveMinimum and ExclusiveMaximum change from type boolean to type number #1271

[felschr]

I'm particularly interested in the new prefixItems option from the JSON schema specification, which can be used for supporting tuples as arrays:
https://stackoverflow.com/questions/57464633/how-to-define-a-json-array-with-concrete-item-definition-for-every-index-i-e-a

[gregsdennis]

@darrelmiller do you have an ETA on this? Do you need help?

[darrelmiller]

It is currently planned as a stretch goal for CY2022H2.

[baywet]

I believe dictionary support is missing from the list microsoft/kiota#62

[KeithMAtFis]

One thing that i would like to see is support for readOnly on properties that are using $ref. for example

[gregsdennis]

@KeithMAtFis I have good news for you!

Previously, $ref meant that sibling keywords were ignored.

But since OpenAPI 3.1 uses JSON Schema 2020-12, this restriction is lifted, and now sibling keywords are respected.

Your use case should work as long as the package does something with the readonly annotation (I have no reason to believe it won't).

[KeithMAtFis]

@gregsdennis that is great. I should have provided some background, I am using Minimal API and DOTNet 6, C#10 and it seems that that does not support OpenAPI 3.1.0 yet in its current form. Out of the box there is Swagger support but it seems to only support 3.0.1 and backwards support to v2. I have not found a way to allow output to 3.1.0 standards.

The Nugets that I am using are Swashbuckle.AspNetCore, Swashbuckle.AspNetCore.Swagger and Swashbuckle.Core all at version 6.4.0 (latest). Would you know if there is another NuGet that I should be using or certain configuration i should use?

Btw, I really appreciate you taking the time to respond.

(here is the GITHUB link to support 3.1.0 in Swashbuckle domaindrivendev/Swashbuckle.AspNetCore#2349)

[gregsdennis]

I don't know of any others, no.

It looks like Swashbuckle is dependent upon this lib, so the goal is to get this one going first.