rubyforgood / rubyforgood/alongwithyou
Tab/screen naming and theme-mapping inconsistencies
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 4
- Avg merge
- 9h 34m
- Merged PRs (30d)
- 16
Description
mobile/src/app/explore.tsx still exports TabTwoScreen; native tab triggers are named index/tasks/explore while web uses home/tasks/explore; the scheme === 'unspecified' ? 'light' : scheme mapping is duplicated in use-theme.ts, app-tabs.tsx, and app-tabs.web.tsx instead of going through useTheme().
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 with mobile/src/app/explore.tsx, use-theme.ts, app-tabs.tsx, and app-tabs.web.tsx. Compare the exported screen name, native and web tab trigger names, and theme mapping across these files. Done means the names are consistent and theme resolution goes through useTheme() without duplicated mapping.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, mobile
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100