testing-library / testing-library/angular-testing-library
Migration path towards /zoneless
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 792
- Forks
- 95
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
Should the /zoneless subpackage become the default.
If so, how should we do it without creating too much hassle to existing codebases?
Proposal:
- re-export the current library as a
/zone(?) sub package => feature release - provide a schematic to update existing import paths to
/zoneand flag thezonesub package as deprecated => feature release - make
/zonelessthe default (with a migration schematic) and remove the/zonelesssub package => major change
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 by comparing the existing /zone and /zoneless subpackages and reviewing how consumers import them. Trace the current package and migration structure before deciding whether the proposed re-export, deprecation, and schematics are feasible. Done means an agreed migration plan that defines compatibility, import changes, and the major-release transition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100