[Feature request] http-server-csharp: Expand output-type to support multiple choice: controllers, models, etc.

[abatishchev]

Clear and concise description of the problem

Earlier, the ProviderHub package supported multi-choice configuration key:

"code-kind": "controller | model | default: both"

Can the new HttpServer package support something similar to that via the already configuration key output-type?

Specifically, what I want to generate:

• models
• controllers

What I don't want:

• docs/*.md
• Program.cs
• README.md

Checklist

• Follow our Code of Conduct
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[github-actions]

🎯 Issue Triage

Feature request to support selective code generation in the http-server-csharp emitter — specifically, the ability to choose which artifacts to generate (e.g., models, controllers) and exclude others (e.g., docs, Program.cs, README.md).

Category: Feature Request
Area: emitter:service:csharp

🔍 Analysis

• The user references a prior ProviderHub package that supported a code-kind configuration option (e.g., "controller | model | default: both").
• The request is to bring similar granularity to the http-server-csharp emitter so consumers can opt in/out of specific generated file types.
• This would be a new emitter option, likely surfaced via tspconfig.yaml or emitter options in package.json.
• No existing duplicate found.

📝 Suggested next steps

• Evaluate feasibility of adding an emitter option (e.g., emit) to filter generated artifact types (model, controller, program, docs, readme, etc.)
• Consider alignment with how other emitters (e.g., http-client-csharp) expose similar configuration
• Design the option schema and document defaults

Generated by Agentic Triage

[markcowl]

Mark Cowlishaw (@markcowl) update doc and point alex at the right setting