Refactor Rename on string parameters for symbol named parameters

Search Terms

Refactor Rename Symbol Named Parameters

Suggestion

Refactor Rename on string parameters (symbol named properties)

Use Cases

If you refactor rename a method every "reference" should be renamed.
Even the string parameter in e.g. jasmin.createSpyObj:

Examples

This

class MyService 
{
	public myMethod(n: number) {
		return n;
	}
}

const myServiceSpy = jasmine.createSpyObj<MyService>(['myMethod']);
myServiceSpy.myMethod.withArgs(999).and.returnValue(1);

should become

class MyService 
{
	public renamedMethod(n: number) {
		return n;
	}
}

const myServiceSpy = jasmine.createSpyObj<MyService>(['renamedMethod']);
myServiceSpy.renamedMethod.withArgs(999).and.returnValue(1);

after refactor rename.

Checklist

My suggestion meets these guidelines:

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
• This feature would agree with the rest of TypeScript's Design Goals.

No implementation file or test is named. Start by locating TypeScript's Refactor Rename entry point and its tests, then trace how symbol references are collected for string parameters. Done means renaming a method also updates matching string names in cases such as jasmine.createSpyObj, without changing unrelated strings.