[emitter] Review comment with duplicated models to report errors for mgmt duplicated models

[MaryGao]

Background

During the SDK release phase, we often receive review comments on public APIs that require the service team to modify the original specification and regenerate the SDK. This frequently leads to multiple rounds of back-and-forth discussions. It would be beneficial to revisit these cases and determine:

• Whether the issue can be addressed on the emitter side, or
• Whether the emitter or TCGC should report errors or diagnostics earlier.

Review Comment

This is a case where the AI flags duplicated models generated, which is unexpected. The _1 suffix is auto-generated to resolve a name collision between two distinct models mapped to the same TypeSpec name, which is a sign of duplicated or ambiguously-named models in the spec.

• Example: [AutoPR @azure-arm-alertsmanagement]-generated-from-SDK Generation - JS-6006122 azure-sdk-for-js#37633 (comment)

Suggestion

It depends on if we need to generate all models as the same namespace

• if yes, report errors for duplicated models and resolve them in validation phase and this would apply to mgmt SDKs.
• if no, resolve conflicts then.

[MaryGao]

@JialinHuang803 could you help confirm if your pr #3810 could report errors for this case so that we could detect this early? Thanks!

[JialinHuang803]

@JialinHuang803 could you help confirm if your pr #3810 could report errors for this case so that we could detect this early? Thanks!

The duplicate-models errors will be successfully detected by TCGC only when the namespace option is set for JS in tspconfig.yaml. With this PR, those errors will be reported if they are detected by TCGC.

[MaryGao]

@kazrael2119 Could you help confirm if the duplicated models could be detected in Jialin's PR?

[kazrael2119]

As Jialin saying, only we add an option namespace in tspconfig.yaml, our emitter will report duplicated model error in tcgc side: