Expose APIs for Allowing Back Compatibility to be Applied To Other TypeProviders

[jorgerangel-msft]

An example is that in ClientProvider we have back compat support for re-adding back methods. This isn't applicable for the mgmt plane generator since they do not utilize ClientProvider. We should consider exposing APIs that allow callers to utilize back compatibility functionality from MTG, with more than one type provider.

[github-actions]

🎯 Issue Triage

This is a feature request to expose back-compatibility APIs from the C# client emitter so they can be used by callers with type providers other than ClientProvider (e.g., the mgmt plane generator).

Category: Feature Request
Area: emitter:client:csharp

🔍 Analysis

• Currently, back-compat support (e.g., re-adding methods) lives inside ClientProvider and is not accessible to other type providers.
• The mgmt plane generator does not use ClientProvider, so it cannot leverage existing back-compat functionality.
• The request is to refactor or expose these APIs so multiple type providers can consume them.
• No duplicate issues found.

📝 Suggested next steps

• Identify which back-compat APIs in ClientProvider should be extracted/exposed.
• Design a public API surface that is provider-agnostic.
• Update the mgmt plane generator to consume the new APIs.
• Add tests covering the new API with non-ClientProvider type providers.

Generated by Agentic Triage