OpenApi 9.0.9 - Incorrect reference types for classes with more than one collection properties of the same reference type

[vukispasic]

I have checked this with the latest 9.0.400 release of ASP.NET Core. The original issue is not yet fixed. The collection references are not even pointing to a type anymore. This is what the generated open api document looks like now.

CC: @RachitMalik12 @captainsafia @MaggieKimani1

{
  ...
  "components": {
    "schemas": {
     ...
     "LegalEntity": {
       "required": [
         "balances",
         "assets",
         "equities",
         "deletedAccounts"
       ],
       "type": "object",
       "properties": {
         "balances": {
           "type": "array",
           "items": {
             "$ref": "#/components/schemas/Account"
           }
         },
         "assets": {
           "type": "array",
           "items": { }
         },
         "equities": {
           "type": "array",
           "items": { }
         },
         "deletedAccounts": {
           "type": "array",
           "items": {
             "type": "integer",
             "format": "int32"
           }
         }
       }
     },
    }
  }
}

The sample repo is also now updated.

Originally posted by @asankaf in #2254

I stumble up on identical issue with our data model, and I am experiencing same issue as @asankaf reported. Starting from 9.0.4 there is no error in top of Swagger UI displayed anymore, but schema is still not generated correctly

[kevingostomski]

dotnet/aspnetcore#62079

It looks like only fixed in .NET 10. I stumble upon this too...

But I still need to validate if .NET 10 RC Release fixed it for my case also

[baywet]

Hi everyone,
Thank you for using the SDK and for reaching out.

For information, the implementation of the schema emission (how dotnet types get transformed to OpenAPISchemas) lives in the asp.net OpenAPI layer.

Issues should be opened there instead of this repository https://github.com/dotnet/aspnetcore/

And yes, net 10 brings major improvements in schema generation (in addition to bringing support for OpenAPI 3.1)

Closing.

[vukispasic]

Hello @baywet

Can you please explain me if your answer mean that there will be no fixes to this bug in .NET 9 and you suggest migrating to .NET 10?

[baywet]

I am saying that this is the wrong repository to report this issue and you should instead report it to the other repository I linked in my previous message.