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
Currently, the endpoints generated via OpenAPI are all in one class/interface. This prevents the ability to component-ize the implementation of the endpoints and prevents good practices, such as separation of concerns.
Describe the solution you’d like
The OpenAPI generation should be modified to set the useTags configuration option to true:
for the server API generation. Note that the generator will still generate the single API, so this should not require any changes to the implementation.
Acceptance Criteria
Separate interfaces are generated for each "domain" in the server API
No modification required for existing implementation
All tests pass/API continues to function as expected
The text was updated successfully, but these errors were encountered:
Tell us about the problem you're trying to solve
Currently, the endpoints generated via OpenAPI are all in one class/interface. This prevents the ability to component-ize the implementation of the endpoints and prevents good practices, such as separation of concerns.
Describe the solution you’d like
The OpenAPI generation should be modified to set the
useTags
configuration option totrue
:for the server API generation. Note that the generator will still generate the single API, so this should not require any changes to the implementation.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: