tsp-naming-collision

Java codegen appends a '1' suffix to parameter names when TypeSpec model names clash with synthetic body types. This naming collision occurs because the generator disambiguates conflicting names automatically during client generation.

To fix Java codegen naming collisions, apply `@@clientName` directives in your TypeSpec definitions to rename the colliding models. Regenerate the Java client using the `tsp-client` tool to produce clean parameter names without suffixes.

Trace the '1' suffix by identifying the generated Java client method and its implementation model, then locate the specific TypeSpec model causing the naming conflict. The collision happens when a model name matches a synthetic body type name.

Yes, resolving naming collisions requires local TypeSpec files to apply `@@clientName` overrides and the `tsp-client` tool to regenerate the Java SDK. These are necessary to rename colliding models and produce updated client code.

Yes, `@@clientName` in TypeSpec is the directive used to rename models clashing with synthetic body types. Applying it to the colliding model prevents the Java codegen from generating parameter names with a '1' suffix.

A limitation is that fixing collisions requires manual identification of which TypeSpec models clash with synthetic body types. You must correctly apply `@@clientName` directives and rerun the `tsp-client` tool; otherwise, the '1' suffix persists in generated Java methods.