Skip to content

[docs-sync] Update documentation for recent code changes - #13

Draft
github-actions[bot] wants to merge 1 commit into
mainfrom
docs-sync/update-2026-08-17-eabe9af325d9d8bf
Draft

github-actions[bot] wants to merge 1 commit into
mainfrom
docs-sync/update-2026-08-17-eabe9af325d9d8bf

Conversation

@github-actions

Copy link
Copy Markdown

Summary

This PR adds documentation for a behavioral change in the @azure-tools/typespec-ts emitter introduced in commit dae0917.

What changed in code

Commit: [typespec-ts] Rename reserved-word operations using singularized group name (Azure#5154)

Reserved-word operations (e.g. delete, in, new) that belong to an operation group are now renamed by appending the singularized operation group name instead of emitting a $-guarded name with a @fixme doc comment.

For example, a delete operation in a Conversations interface now generates deleteConversation instead of $delete.

Documentation added

  • New page: website/src/content/docs/docs/emitters/clients/typespec-ts/operation-naming.md
    • Explains the automatic rename behavior for reserved-word operations in operation groups
    • Documents the @clientName escape hatch for opting out of the rename
    • Covers the fallback behavior for top-level operations (no group)
    • Notes the intentional exception for ARM/management-plane packages

Generated by Documentation Sync · 34.3 AIC · ⌖ 7.01 AIC · ⊞ 5.5K · ◷

Document the reserved-word operation renaming behavior introduced in
commit dae0917: operations like 'delete' inside operation groups are
now automatically renamed by appending the singularized group name
(e.g., deleteConversation). Document the @clientName escape hatch,
top-level operation fallback, and the intentional ARM exception.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants