Export the IconSource type from react-native-paper
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- react-native, typescript
- Domain
- developer-experience, mobile-dev
Research direction
Read the package's public type export entry points and locate where other component types are re-exported. Export IconSource so import type { IconSource } from 'react-native-paper' works, then run the relevant type or package export checks; done when consumers can import it from the package root without a deep import.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
Most icon props take Paper's IconSource type, but react-native-paper doesn't export it. In 5.x apps imported it from react-native-paper/lib/typescript/components/Icon; in 6.x that path moved to lib/typescript/src/components/Icon, so those imports break on upgrade.
Describe the solution you'd like
import type { IconSource } from 'react-native-paper' works.
Describe alternatives you've considered
type IconSource = React.ComponentProps<typeof Icon>['source'] works today without a deep import.
Additional context
A new export, so it fits a 6.x minor.
- Dominant language
- TypeScript
- Stars
- 14.5k
- Forks
- 2.3k
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 22
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 callstack/react-native-paper
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
callstack/react-native-paper#5187 ·
Maintainers usually reply within 1 day
-
Accessibility example app good first task
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
callstack/react-native-paper#5182 ·
Maintainers usually reply within 1 day
-
Accessibility bug web
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
callstack/react-native-paper#5180 ·
Maintainers usually reply within 1 day
-
Chip: accessibilityState passed by caller is discarded; aria-checked is never forwarded to the real rendered nodePossibly taken @bhumikabiyani claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
callstack/react-native-paper#5146 · 2 comments ·
Maintainers usually reply within 1 day
-
Tooltip: onPress event object is not propagated to parent component on nativePossibly taken @aliyilmaztech claimed this 86 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
callstack/react-native-paper#5003 ·
Maintainers usually reply within 1 day
All issues in callstack/react-native-paper
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
pending close triaging
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
anomalyco/opencode#62582 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
live-codes/livecodes#1079 · 1 comment ·
Maintainers usually reply within 1 day
-
Add: ESP 2 ROOpenapproved check:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day