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
The concept of an area in ATC generated code is used to control names of controllers, folders etc. This is today based solely on the root element of the api path. In some cases this is not ideal and this is a request to be able to control this.
An example is if multiple services are serving part of an api that share a common root element and it is actually a sub-element of the path that logically defines the area for each service.
Idea for solution
Be able to specify area name in the OpenApi file for each operation. Using the OpenApi spec for this will make it very clear how the area is linked to the generated code.
The text was updated successfully, but these errors were encountered:
Problem
The concept of an area in ATC generated code is used to control names of controllers, folders etc. This is today based solely on the root element of the api path. In some cases this is not ideal and this is a request to be able to control this.
An example is if multiple services are serving part of an api that share a common root element and it is actually a sub-element of the path that logically defines the area for each service.
Idea for solution
Be able to specify area name in the OpenApi file for each operation. Using the OpenApi spec for this will make it very clear how the area is linked to the generated code.
The text was updated successfully, but these errors were encountered: