Rely on NextJS Router for some state
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Some of our "pages" should probably use the router instead of relying on state like we are.
Namely, the follow pages should be updated:
| Old location | New path |
| ---------------- | ------------------------------------------ |
| Questions tab | `/host` |
| Leaderboard tab | `/host/leaderboard` |
| Teams tab | `/host/teams` |
| Inspect team | `/host/teams/` |
| Team submissions | `/host/teams//` |
| Bulk team gen | `/host/teams/generate` |
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the host pages for the Questions, Leaderboard, Teams, Inspect team, Team submissions, and Bulk team gen views, then inspect how their navigation currently relies on state. Verify the listed /host routes and dynamic team and question paths, and consider the work done when each view is reachable at its specified URL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, typescript
- Domain
- frontend, web-dev
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100