OpenAPITools / OpenAPITools/openapi-generator
[REQ] [aspnetcore] Separate controller for each route and/or model
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
Is your feature request related to a problem? Please describe.
I'm not sure if this is a bug or if it is simply not implemented, but it would be good to be able to have one controller generated per model and/or route, instead of all controller actions going into one controller (DefaultApiController, in DefaultApi.cs)
Describe the solution you'd like
For example, if my models were Foo and Bar, then I'd want something like FoosController and BarsController to be generated
Describe alternatives you've considered
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the ASP.NET Core generator entry points and the generated DefaultApiController in DefaultApi.cs. Determine how models and routes are currently grouped, then define how generation should produce separate FoosController and BarsController outputs and what generated results would confirm the feature is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100