Name the selected term in the /plans empty state
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 86/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- next.js, react, typescript
- Domain
- frontend
Research direction
Read src/app/plans/(list)/layout.tsx and the useTerm() provider in src/components/providers/TermProvider.tsx; inspect the savedPlans.length === 0 branch and how the selected term matches availableTerms. Update the empty state to name the term while keeping the “Create a Plan” button, and fall back to the existing wording when no description is found. Confirm switching terms changes the heading and run the checks listed in the issue.
Written by the indexing model from the issue text.
Description
What to build
When the selected term has no saved plans, the empty state on /plans says "You don't have any saved plans yet." with no hint of which term it means, and the term picker is easy to miss. Make the empty state name the selected term (for example "You don't have any saved plans for Spring 2027 yet.") and keep the "Create a Plan" button.
Note: the original queue asked for the empty state itself; it has since landed, so this issue is its remaining gap.
The file it touches
src/app/plans/(list)/layout.tsx (the empty-state branch, savedPlans.length === 0). The selected term comes from useTerm() in src/components/providers/TermProvider.tsx; availableTerms has each term's description.
Acceptance check
- With no plans, the heading names the selected term; switching the term in the navbar changes the text.
- If the term's description cannot be found, the old wording is shown (no "undefined").
pnpm test,pnpm lint,pnpm typecheckpass. Screenshot of the empty state in the PR.
New here? Setup is in docs/getting-started/setup.md; the first-PR walk-through is docs/getting-started/first-contribution.md.
- Dominant language
- TypeScript
- Stars
- 19
- Forks
- 94
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from DevDogsUGA/DogDays
-
import-export
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
DevDogsUGA/DogDays#788 ·
-
import-export
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
DevDogsUGA/DogDays#785 ·
-
Frontend time-gaps
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
DevDogsUGA/DogDays#784 ·
-
good first issue polish
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
DevDogsUGA/DogDays#780 ·
-
good first issue polish
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
DevDogsUGA/DogDays#779 ·
All issues in DevDogsUGA/DogDays
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
Zettlr/Zettlr#6610 · 1 comment ·
Maintainers usually reply within 1 day
-
Feil lovtekst i bekreftelsen når leder melder unntak fra oppfølgingsplanPossibly taken @AudunSorheim claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
navikt/syfo-oppfolgingsplan-frontend#1110 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
db-ux-design-system/core-web#8461 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Cannot run an integration on windows when power shell is selected as the default profile terminalOpenPriority/Blocker Type/Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
wso2/product-integrator#2767 ·
Maintainers usually reply within 1 day