Tab/screen naming and theme-mapping inconsistencies

Open Beginner friendly
#93 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
frontend, mobile

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.

Description

good first issue severity:minor

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().

Dominant language
TypeScript
Stars
9
Forks
4
Avg merge
9h 34m
Merged PRs (30d)
16

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rubyforgood/alongwithyou

All issues in rubyforgood/alongwithyou

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.