Fix @actionSeparator decorator to accept Operation, Interface, and Namespace targets with hierarchy support

[Copilot]

✅ Fix @actionSeparator decorator target validation and hierarchy behavior - COMPLETED

Successfully narrowed the @actionSeparator decorator targets from Model | ModelProperty | Operation to Operation | Interface | Namespace and implemented proper hierarchy behavior where separators can be applied at namespace or interface level and automatically propagate to contained operations.

✅ Completed Tasks:

• Analyze current implementation and reproduce the issue
• Verify current tests pass
• Update the TypeScript decorator function signature to accept only Operation | Interface | Namespace
• Update the TypeSpec decorator definition in rest-decorators.tsp to match
• Update generated TypeScript definitions
• Add comprehensive validation tests for each allowed target type
• Implement hierarchy lookup logic for namespace and interface targets
• Add tests for hierarchy and override behavior
• Run tests to ensure no regressions - ALL 64 tests pass ✅
• Update README and website documentation with hierarchy explanation
• Test the fix manually with reproduction case - SUCCESSFUL ✅
• Merge latest changes from main branch
• Add changelog entry using chronus
• Fix formatting issues with pnpm format
• Include generated TypeSpec definitions in PR
• Address code review feedback (backticks, describe blocks, decorator style)

✅ Fix Summary:

Issue resolved: @actionSeparator now correctly accepts only Operation, Interface, and Namespace as targets, and properly rejects Model and ModelProperty targets. The decorator implements a hierarchy system where:

• Namespace-level: Separator applies to all action operations in the namespace and its sub-namespaces (recursively)
• Interface-level: Separator applies to all action operations in the interface and overrides namespace-level separators
• Operation-level: Separator applies only to that operation and overrides both interface and namespace-level separators

✅ Validation Results:

1. Target Validation Working Correctly:

• ✅ @actionSeparator on Operations: Works and affects routing
• ✅ @actionSeparator on Interfaces: Applies to all operations in interface
• ✅ @actionSeparator on Namespaces: Applies to all operations in namespace and sub-namespaces
• ✅ @actionSeparator on Models: Correctly rejected with proper error message
• ✅ @actionSeparator on ModelProperties: Correctly rejected with proper error message

2. Hierarchy Behavior:

• ✅ Interface-level separator applies to all actions in interface
• ✅ Namespace-level separator applies to all actions in namespace and sub-namespaces
• ✅ Operation-level separator overrides interface-level separator
• ✅ Interface-level separator overrides namespace-level separator
• ✅ Proper recursive lookup through namespace hierarchy

3. Functionality Tests:

• ✅ All separator values (/, :, /:) work correctly in routing
• ✅ Operations with @actionSeparator generate correct route paths
• ✅ Original reproduction case now compiles successfully
• ✅ Invalid usage cases are properly rejected with clear error messages

4. Regression Tests:

• ✅ All existing tests continue to pass (64/64 tests pass)
• ✅ No breaking changes to existing functionality
• ✅ Route generation works as expected

📁 Files Modified:

• packages/rest/src/rest.ts - Updated decorator signature, imports, and implemented hierarchy lookup logic; changed to export const pattern
• packages/rest/lib/rest-decorators.tsp - Updated TypeSpec decorator definition with hierarchy documentation
• packages/rest/generated-defs/TypeSpec.Rest.ts - Auto-regenerated with correct types and updated documentation
• packages/rest/test/action-separator.test.ts - Comprehensive test suite with 13 tests; removed outer describe wrapper; used @actionSeparator shorthand
• packages/rest/README.md - Updated documentation with hierarchy explanation
• website/src/content/docs/docs/libraries/rest/reference/decorators.md - Regenerated documentation
• .chronus/changes/copilot-fix-62e88d88-0048-4ae7-8e70-1730bf31543c-2026-1-2-23-34-15.md - Changelog entry (with backticks)

🎯 Impact:

The fix resolves the original issue where @actionSeparator was incorrectly allowing Model and ModelProperty targets that didn't work properly. Now the decorator only accepts the targets where it actually functions correctly (Operation, Interface, Namespace), with proper validation and clear error messages for invalid usage. Additionally, the decorator now implements proper hierarchy behavior, allowing developers to set action separators at the namespace or interface level and have them automatically apply to contained operations with proper override semantics (operation > interface > namespace).

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[Bug]: @actionSerparator works only when defined on operation, but allowed on models and models properties</issue_title>
<issue_description>### Describe the bug

There's no well written documentation on how to use it either, so it might be that I'm doing it wrong.

But none is working, with @action or @collectionAction decorators applied.

Reproduction

https://typespec.io/playground/?e=%40typespec%2Fopenapi3&c=aW1wb3J0ICJAdHlwZXNwZWMvaHR0cCI7CtIZcmVzdCI7Cgp1c2luZyBIdHRwO8cMUmVzdDsKCkBzZXJ2aWNlCm5hbWVzcGFjZSBUxBogCgoKQHJvdXRlKCJvbi1vcCIpyyNPbk9wIHsKICBAYXV0b1LEJ8UNY3Rpb27KClNlcGFyYXRvcigiOiIpCiAgb3AgZG8oKTogdm9pZDsKfc1kbW9kZWzPZ03EFMdq1lPFNiBFbnRpdHnFKSAgaWQ6IHN0cmluZzsKICB9CvEAqGNvbGxlxU9BxQYoxj%2FET8dn%2FwCs5gCsLXByb3BldHn0ALRQxBty5wCT8wCk%2BADP%2FwC%2B%2FwC%2B%2BgC%2B&options=%7B%7D&vs=%7B%7D

Checklist

• Follow our Code of Conduct
• Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion.
• The provided reproduction is a minimal reproducible example of the bug.</issue_description>

<agent_instructions>Narrow the target of the @actionSeparator to include only operations, interfaces, and namespaces. Ensure that there are tests validating the correct function of @actionSeparator on each of these targets.</agent_instructions>

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

Fixes #8589

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[markcowl]

@copilot please reopen this pull request and pull in the latest changes from the main branch

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/microsoft/typespec/@typespec/rest@8609

commit: 78184b4

[github-actions]

All changed packages have been documented.

• ✅ @typespec/rest

Show changes

@typespec/rest - fix ✏️

Fix @actionSeparator decorator to only accept Operation, Interface, and Namespace targets

[markcowl]

@copilot please add a description of this change using pnpm chronus add

[Copilot]

@copilot please reopen this pull request and pull in the latest changes from the main branch

The pull request has been updated with the latest changes from main (commit 7cbbe36). All tests pass successfully (58/58). The merge brought in recent changes including commits 6a3107a, a8ba8b1, and e717674 from main, and there are no conflicts or test failures.

[Copilot]

@copilot please add a description of this change using pnpm chronus add

Changelog entry added in commit 2abb35a. The change is categorized as a "Bug Fix" for the @typespec/rest package.

[markcowl]

@copilot This pull request seems unlikely to change the actionSeparator used in operation routes, unless the decorator is applied to an operation. Please update the implementation so that instances of @actionSeparator applied to interfaces change the action separator for each action operation in the interface. Similarly, please update the implementation so that instances of @actionSeparator applied to the namespace change the action separator for each action operation in the namespace (including in subnamespaces and in interfaces in the namespace and its subnamespaces). Finally, ensure that an @actionSeparator applied to an interface will override an @actionSeparator applied to the namespace containing that interface. Similarly, ensure that an @actionSeparator applied to an operation will override any @actionSeparator applied to the operation's interface or namespace.

Please also re-generate documentation for the decorator

[Copilot]

@copilot This pull request seems unlikely to change the actionSeparator used in operation routes, unless the decorator is applied to an operation. Please update the implementation so that instances o...

Implemented in commit 3c2e1c1. The @actionSeparator decorator now properly implements hierarchy behavior:

• Namespace-level: Applies to all action operations in the namespace and sub-namespaces (recursively)
• Interface-level: Applies to all action operations in the interface and overrides namespace-level separators
• Operation-level: Applies only to that operation and overrides both interface and namespace-level separators

Added 6 comprehensive tests validating all hierarchy and override scenarios. Documentation has been updated in the TypeSpec decorator definition, README, and website docs to explain the hierarchy behavior.

[Copilot]

@copilot the PR is failing due to formatting and because building the @tpespec/rest package makes changes to generated typespec definitions. Please run pnpm format to fix the formatting of all files ...

Fixed in commit be5887b. Ran pnpm format to fix formatting issues (whitespace) and regenerated TypeSpec definitions using tspd gen-extern-signature. All generated changes are now included in the PR.

[markcowl]

/azp run typespec - PR Tools

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[azure-sdk]

You can try these changes here

🛝 Playground	🌐 Website	🛝 VSCode Extension