no-corresponding-method-param
@azure-tools/typespec-client-generator-core/no-corresponding-method-paramSeverity: error
This diagnostic is issued when a required HTTP operation parameter cannot be mapped to any generated method parameter. The generated client would have no reliable way to supply that required service parameter.
Impact
Section titled “Impact”- Area: Method-to-protocol parameter mapping. Blocks generation of a service method when a required HTTP parameter cannot be supplied by the generated SDK method signature.
- Not affected: The HTTP operation still declares the required parameter.
Diagnostic Message
Section titled “Diagnostic Message”TCGC reports:
Missing HTTP operation parameter "apiVersion" in method "getWidget". Please check the method definition.✅ How to Fix
Section titled “✅ How to Fix”Check any client customization, such as @override, @paramAlias, parameter reordering, or parameter removal, that changes the method parameters, and fix it so every HTTP operation parameter still maps to a method parameter.