OpenAPI incorrectly misses some metadata in swagger spec

[JustArchi]

Checklist

• I read and understood ASF's Contributing guidelines
• I also read Setting-up and FAQ, I don't need help, this is a bug report
• This is not a duplicate of an existing issue
• I don't own more than 10 accounts in total
• I'm not using custom plugins
• This is not a question
• This is not a technical issue
• This is not ASF-ui problem

ASF version

Latest pre-release

ASF variant

generic (with latest .NET runtime)

Bug description

Since changing swagger generator from Swashbuckle to OpenAPI, we're observing an issue with some references in the swagger generator, in particular, dupes that are sometimes incorrect in their definition.

Notable example:

Expected behavior

Actual behavior

Steps to reproduce

No response

Possible reason/solution

This issue remains open while we're waiting for dotnet/aspnetcore#58968 to ship in .NET 9.0.2+, and confirmation from our side that the issue does not happen anymore.

Can you help us with this bug report?

Yes, I can code the solution myself and send a pull request

Full log.txt recorded during reproducing the problem

-

Global ASF.json config file

BotName.json config of all affected bot instances

Additional info

We'll consider this temporary degradation, since the cost of reverting the OpenAPI generator is much higher than temporary inconvenience from missing x-definition, among other properties.

[JustArchi]

I've decided that reverting back to Swashbuckle is required in regards to breaking changes on ASF-ui side.

For people keen on experimenting, ASF temporarily offers undocumented otherwise --use-openapi cmdline switch, which will force OpenAPI instead of Swashbuckle for swagger generation. It's expected that this option will become default starting from .NET 9.0.2, when the issue mentioned here gets resolved. Until then it's offered for experiments only, as it's known to generate imperfect schema.

If appropriate workaround for dotnet/aspnetcore#58968 is found earlier, and resolving at least the more critical breaking changes, the switch might happen sooner.

[JustArchi]

@zerox003 Feel free to review if V6.1.3.1 still works for your use cases. Yes, the schema has changed, but it should no longer change in a way you can't extract the data you need (all enums carry x-definition now).