[ASPNETCORE] multiple tags for a method generates multiple controllers

Description

Multiple tags create multiple server endpoints

openapi-generator version

4.0.0-beta3

OpenAPI declaration file content or url

This is more a query (is there not a ML/community for this sort of thing?).

I've declared tags in the OpenAPI specification, to thematically collect API calls around various use-cases.

Thus API methods may have several tags. This is very useful in documentation generation.

But when aspnetcore generation occurs, you get a controller per tag - which doesn't seem right at all - not least of which the URL is identical in both.

There seems to be an assumption that a method has only one tag (maybe?) for the server end.

There doesn't seem to be a nice way to split up big APIs in OpenAPI that works nicely. Unless I'm missing something..

Start by reproducing the issue with the ASP.NET Core generator and an OpenAPI declaration where one operation has multiple tags. Inspect the generated controllers and compare their identical URLs; done should mean the generator's handling of multi-tag operations matches the intended server behavior, with coverage for the reproduced case.