callstack / callstack/react-native-paper
feat: add Navigation Rail
- Dominant language
- TypeScript
- Stars
- 14.5k
- Forks
- 2.2k
- Avg merge
- 5d 23h
- Merged PRs (30d)
- 12
Description
The goal is to implement the Navigation Rail according to specs, a component replacing the old Drawer.
- See specs: https://m3.material.io/components/navigation-rail/overview.
- Reuse newly introduced tokens (shape, motion, typography, color etc)
- Extract component specific tokens for easier maintenance.
- Get inspired from TextInput/TextField, Switch, Checkbox, FAB components which have gone through modernization.
Contributor guide
Research direction
Start with the Material 3 Navigation Rail specifications, then inspect the existing Drawer and the modernization work in TextInput/TextField, Switch, Checkbox, and FAB. Trace how those components use the new shape, motion, typography, and color tokens. Done means a Navigation Rail component replaces the old Drawer behavior and uses maintainable component-specific tokens.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- frontend, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100