microsoft / microsoft/TypeScript
quick fix for merge duplicate import or export declaration
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
Search Terms
quickfix, import, export
Suggestion
provide a quickfix for merge two(or more) import or export declaration
Use Cases
it's useful for resolve git conflict
Examples
// ====
import { a, b, c } from 'mod'
// ====
import { b, d, e } from 'mod'
// ====
keep each other for git conflict:
import { a, b, c } from 'mod'
import { b, d, e } from 'mod'
after merge:
import { a, b, c, d, e } from 'mod'
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. new expression-level syntax)
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
The issue provides only TypeScript examples and no source file, test, or entry point. Start by locating the quick-fix implementation for import and export declarations, then determine how duplicate declarations should be merged without changing runtime behavior. Done means the requested conflict-resolution quick fix works for the shown imports and has coverage for the resulting merged declaration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100