[refactoring]
Applies TypeScript language-service rename edits for a symbol after computing the plan.
JS/TS renames should follow language-service identity rather than search-and-replace text.
The model can preview or apply semantic rename plans with affected files and diagnostics evidence.
Try it locally in the TGlider playground
| Name | Type | Required | Description |
|---|---|---|---|
| symbolKey | string | Yes | Stable symbol key returned by a prior symbol discovery tool. |
| newName | string | Yes | New symbol name. |
| scope | string | No | Rename scope: 'same-project', 'direct-dependents', or 'transitive-dependents'. |
| allowPartial | boolean | No | Allow applying a partial rename when some projects cannot be resolved safely. |
Apply a semantic rename
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "rename_symbol",
"arguments": {
"symbolKey": "role=canonical|...",
"newName": "AccountService"
}
}
}Returns applied files, occurrence counts, skipped projects, and post-apply diagnostics.