OpenAPI incorrectly misses some metadata in swagger spec #3376
Open
Description
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.
Metadata
Assignees
Labels
Issues marked with this label have external scope and typically depend on third-party projects.Issues marked with this label are blocked from being worked on, very often due to third-parties.Issues marked with this label were acknowledged and confirmed by the developers.Issues marked with this label indicate unintended program behaviour that needs correction.