jamesplease / jamesplease/router-comparison
Add State/Route abstraction
Open
- Dominant language
- No language data
- Stars
- 38
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Angular v2/React Router skip the "Route" / "State" abstraction altogether and jump straight to a component, then use the component's lifecycle rather than route lifecycle methods.
This is worth discussing more in this doc!
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue concerns the client-side router comparison and mentions Angular v2 and React Router; start by reading the existing comparison document and its treatment of Route and State. Done means expanding the relevant documentation to explain how those routers use components and component lifecycle methods instead.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, react
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100