Is OpenAPI 3.1.0 supported ?

[gautamnabin5]

Was wondering if .NET core code generation using open api spec file version 3.1.0 is supported ?

[stevenvolckaert]

I'm having the same question.

@RicoSuter is OpenAPI 3.1.0 supported by the latest NSwag.MSBuild version, v13.16.0?

Thank you!

[SimonCull]

Also interested in this.

[jhancock4d]

For me, I'm specifically interested in OpenAPI 3.1 for the following cases:

1. Defininig enums using OneOf and having maps of values to descriptive text.
2. Response generics so that we can return things like an IAsyncEnumerable of items of whatever type we want, and say a totalCount and a few other things and not have it generate a bazillion different types for no reason.

[glyad]

Waiting for an answer...

[amrud]

interested in this too...

[trenslow]

did anyone get an answer for this?

[dlgombert]

Hi. Please tell.

[andrewmshea]

Let me know :(

[amilos]

Answer would be appreciated :)

[meiedomi]

We are currently evaluating NSwag for our new project using OpenAPI 3.1 too, but I couldn't find any official information regarding the support for 3.1. Any updates?

[lahma]

If there's someone on this thread being both technically apt and having understanding of the 3.1 spec it might be pretty useful to test it against v14 preview and report what is missing instead of asking if someone could test it on your behalf. If it helps I can always start to ping everyone asking about "any updates with testing it?" 🙄

[JohnGalt1717]

Doesn't appear to move the ball forward at all on any of these things.

Enums need oneOf support
Generics need to be supported (which right now just throw a horrible error message that tells you nothing)

If someone needs it, here's a SchemaFilter for the enums support:

public sealed class FixNSwagEnumsProcessor : ISchemaProcessor {
	public void Process(SchemaProcessorContext context) {
		if (!context.ContextualType.Type.IsEnum)
			return;
		
		foreach(var item in context.Schema.EnumerationNames.Index()) {
			var enumValue = context.Schema.Enumeration.ElementAt(item.index);
			var enumSchema = new JsonSchema
			{
				ExtensionData = new Dictionary<string, object?>
				{
					{ "const", enumValue },
					{ "title", item.item }
				}
			};

			context.Schema.OneOf.Add(enumSchema);			
		}
	}
}

But generics is a hard break. And it doesn't even do what Swashbuckle does and generate a whole pile of unique ref types for every generic it finds.