Fix TCGC regression with @clientOption negation scope filtering

[Copilot]

• Understand the issue: The filtering logic in getDecoratorsInfo in internal-utils.ts doesn't handle negation scope patterns like !python or !(java, python)
• Identify the fix location: Line 406-411 in /packages/typespec-client-generator-core/src/internal-utils.ts
• Implement fix: Added parseScopes and isScopeApplicable helper functions to properly handle negation scopes
• Add tests for negation scope filtering in client-option.test.ts (6 new tests)
• Run tests to verify the fix (418 tests pass)
• Run code review and address feedback
• Consolidate duplicate parseScopes function (moved from decorators.ts to internal-utils.ts and exported)
• Add changelog entry

Summary

• Fixed a regression where the @clientOption decorator (and other decorators using scope filtering in getDecoratorsInfo) did not properly handle negation scope patterns
• Consolidated the duplicate parseScopes function by moving it to internal-utils.ts and exporting it for use by decorators.ts

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[TCGC] Regression with @clientOption</issue_title>
<issue_description>In this PR, there is a change to filter decorators on types decorators list. It only considered the positive scope case, but fail with negation scope case. For case @clientName("XXX", "!python"), the new added logic will cause regression. The filter should work for negation scope cases.</issue_description>

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

• Fixes [TCGC] Regression with @clientOption #3884

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[pkg-pr-new]

Open in StackBlitz

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

commit: 2e2deee

[tadelesh]

@copilot Resolve comment.

[azure-sdk]

All changed packages have been documented.

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

Show changes

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

Fix regression with @clientoption negation scope handling. Decorators using negation scope patterns like '!python' or '!(java, python)' are now correctly filtered.

[azure-sdk]

You can try these changes here

🛝 Playground	🌐 Website

[Copilot]

@copilot Resolve comment.

Done in 2e2deee.

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/website/node_modules/.bin/../astro/astro.js build sh ore/node_modules/.bin/../@typespec/tspd/cmd/tspd.js astro check --mi--llmstxt node n/node xtern-signature sh ture tobuf/reference node c-cl�� ../../website/src/content/docs/docs/libraries/sse/reference . _modules/pnpm/dist/node-gyp-bin/node --import y-linter nerator-core/reftspd doc . --enable-experimental --output-dir ../../website/src/content/docs/docs/libraries/azure-portal-core/reference node (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)