You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The .NET OpenAPI generator is creating duplicate models when generating from a minimal API setup in .NET 9.
OpenApi File To Reproduce
Steps to reproduce:
Create a .NET 9 minimal API project
Generate OpenAPI specification using the built-in tools
Observe the generated output contains duplicate entries
Expected behavior
The OpenAPI generator should create unique model without any duplication, properly reflecting the minimal API structure.
Screenshots/Code Snippets
Sample1
Sample2
And few others.
The text was updated successfully, but these errors were encountered:
jzs11
changed the title
The .NET OpenAPI generator is creating duplicate code/endpoints when generating from a minimal API setup in .NET 9.
The .NET OpenAPI generator is creating duplicate models when generating from a minimal API setup in .NET 9.
Nov 15, 2024
@jzs11 This repo is for the underlying data model used by ASP.NET Core. I'd recommend that you file this bug on the dotnet/aspnetcore repo for further investigation.
@captainsafia Given your contributions on the openapi work for dotnet9 is this something you can help raise awareness of? As things currently stand, I dont see how the openapi work in dotnet 9 is useable at all for anything but very trivial schemas.
@akamor Yep, this is on my radar. Doing some investigation into the various reports at the moment. I'll post in the issue referenced in this comment once I have something.
Describe the bug
The .NET OpenAPI generator is creating duplicate models when generating from a minimal API setup in .NET 9.
OpenApi File To Reproduce
Steps to reproduce:
Expected behavior
The OpenAPI generator should create unique model without any duplication, properly reflecting the minimal API structure.
Screenshots/Code Snippets

Sample1
Sample2

And few others.
The text was updated successfully, but these errors were encountered: