Add crossLanguageDefinitionId to SdkEnumValueType

[Copilot]

Enum values are referencable entities but lacked crossLanguageDefinitionId, inconsistent with other SDK types.

Changes

• interfaces.ts: Added crossLanguageDefinitionId: string property to SdkEnumValueType interface
• public-utils.ts: Extended getCrossLanguageDefinitionId() to accept EnumMember and generate IDs in format ParentEnum.memberName
• types.ts: Populated crossLanguageDefinitionId in getSdkEnumValueWithDiagnostics() and getSdkUnionEnumValues()
• tests: Added coverage for regular and union enum value IDs

Example

For enum WidgetService.Color { Red, Green, Blue }:

// Enum crossLanguageDefinitionId
"WidgetService.Color"

// Enum value crossLanguageDefinitionIds
"WidgetService.Color.Red"
"WidgetService.Color.Green"
"WidgetService.Color.Blue"

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• telemetry.astro.build
  • Triggering command: /usr/local/bin/node node /home/REDACTED/work/typespec-azure/typespec-azure/core/website/node_modules/.bin/../astro/astro.js build sh core�� ebsite/src/content/docs/docs/emitters/openapi3/reference node s/.bin/sh warn-as-error --sh . rsioning/referentspd doc . --enable-experimental --output-dir ../../website/src/content/docs/d--output-dir node core�� --noEmit node core/node_modules/.bin/node lint-typespec-liuname pnpm s/.bin/sh tp/reference (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[TCGC] enumvalue types should have crossLanguageDefinitionId</issue_title>
<issue_description>As a "referencable" entity, the enumvalue types should have a crossLanguageDefinitionId.

Actually I suggest we move the crossLanguageDefinitionId to the SdkTypeBase type to ensure every SdkType would have this property.</issue_description>

<agent_instructions>1. Add crossLanguageDefinitionId to the SdkEnumValueType type https://github.com/Azure/typespec-azure/blob/main/packages/typespec-client-generator-core/src/interfaces.ts#L470
2. Use this function and update to accept the enum value type https://github.com/Azure/typespec-azure/blob/main/packages/typespec-client-generator-core/src/public-utils.ts#L241 to get the cross language definition id
3. Add tests in this file https://github.com/Azure/typespec-azure/blob/main/packages/typespec-client-generator-core/test/public-utils/get-cross-language-definition-id.test.ts
</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes [TCGC] enumvalue types should have crossLanguageDefinitionId #2834

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/Azure/typespec-azure/@azure-tools/typespec-client-generator-core@3764

commit: 9d6e055

[tadelesh]

Overall LGTM. But I'm wondering if we need to move crossLanguageDefinitionId to the base type.

[iscai-msft]

if we added it to the base type, then we should also have credential, endpoint, tuple, and dictionary types taking on cross language definition id. I think for those it largely makes sense not to have a cross language definition id

[azure-sdk]

All changed packages have been documented.

• ✅ @azure-tools/typespec-client-generator-core

Show changes

@azure-tools/typespec-client-generator-core - feature ✏️

Add .crossLanguageDefinitionId. to SdkEnumValueType

[azure-sdk]

You can try these changes here

🛝 Playground	🌐 Website