microsoft / microsoft/TypeScript
Refactor rename file + rename function
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
Search Terms
Rename refactor move file filename and function name matching
Suggestion
We have a really common pattern: A file of name MyFile.tsx and a matching function of the types:
export default function MyFile() {}
export function MyFile() {}
export const MyFile = () => {}
Use Cases
I find myself constantly doing a two part refactor. First refactor the function, then refactor the filename. Combining the two would save quite a lot of time and encourage better naming everywhere.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the existing rename refactor implementations and their tests, then determine how file renaming and matching function renaming are represented together. Done means the TypeScript and TSX examples support a combined refactor with coverage for the requested declaration forms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100