microsoft / microsoft/TypeScript
Refactor: Introduce object destruction
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
Search Terms
refactor, object destruction
Suggestion
A refactor that extract all property access expression to a object destruction or convert back

Use Cases
Examples
const item = {
a: 1, b: 2
}
call(item.a, item.b)
to
const item = {
a: 1, b: 2
}
const { a, b } = item
call(a, b)
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.
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
Start with the issue's TypeScript examples and the linked Design Goals, then determine the intended scope of converting property-access expressions to object destructuring or back again. No source files, entry points, or tests are named, so locating the relevant compiler transformation and defining coverage would require substantial project familiarity. Done means the specified conversion works without changing emitted JavaScript runtime behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100