feat(http-server-csharp): added include-operations-controller option to skip generating operations controller

[Copilot]

RPaaS and similar hosting platforms handle certain endpoints (e.g., ARM Operations) automatically, making the generated controller and business-logic interface files unnecessary noise.

Changes

• New emitter option exclude-interfaces (string[]) in lib.ts — lists TypeSpec interface names to skip during generation
• emitter.tsx — filters resolved interfaces against the exclusion set before passing to ControllersAndInterfaces, MockImplementations, and mock registration helpers; excluded interfaces produce no *Controller.cs or I*.cs files
• Tests — test/exclude-interfaces.test.ts covers single exclusion, multi-exclusion, no-op exclusion, and baseline (no exclusions)
• Changelog — feature entry for @typespec/http-server-csharp

Usage

# tspconfig.yaml
options:
  "@typespec/http-server-csharp":
    exclude-interfaces:
      - Operations

With the above config, OperationsController.cs and IOperations.cs are not emitted; all other interfaces are unaffected.

• Fixes [Feature request] http-server-csharp: Configuration key to turn of generating Operations controller #11494

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
1 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[abatishchev]

@copilot why it's exclude-interfaces The issue is about Operations controller. Hence the key should be called include-operations-controller of type boolean: include if true, otherwise don't. Default it to false

[Copilot]

Replaced exclude-interfaces with include-operations-controller: boolean (default false). When false (default), the controller and interface for any TypeSpec interface named exactly Operations are not generated. Set to true to include them.

Committed in the latest push.

[abatishchev]

NOTE: this is a breaking change

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@typespec/http-server-csharp@11495

commit: a0cdc89

[github-actions]

All changed packages have been documented.

• ✅ @typespec/http-server-csharp

Show changes

@typespec/http-server-csharp - feature ✏️

Add include-operations-controller emitter option (boolean, default false) to control whether a controller and business-logic interface are generated for the ARM Operations endpoint. Set to true to include the Operations controller.,> ,> yaml,> # tspconfig.yaml,> options:,> "@typespec/http-server-csharp":,> include-operations-controller: true,>

[timotheeguerin]

this is too azure specific, this emitter shouldn't have any reference to azure in its options and handling of things.
I think we might be better of having a generic omit-types: string[] option which lets you exclude any types from being generated. This is still not ideal as this really should be defined with decorators but this is not something we'll have soon so this can unblock in the meantime

[azure-sdk-automation]

You can try these changes here

🛝 Playground	🌐 Website	🛝 VSCode Extension