mgechev / mgechev/angular2-hot-loader
Refactoring
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 113
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
At this point we use the DynamicComponentLoader and render the entire root component in order to refresh the user interface.
This issue has the following implications:
- Performance implication - https://github.com/mgechev/angular2-hot-loader/issues/8
- The component looses its state - https://github.com/mgechev/angular2-hot-loader/issues/11
Contributor guide
No contributing guide indexed for this repository
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 tracing where DynamicComponentLoader is used to refresh the user interface. Review the linked issues about performance and lost component state before defining the scope. Done should address the root-component rendering approach without the listed performance and state implications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100