Feature Request: Add loader prop to <GooglePayButton> component
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- react-native
- Domain
- mobile
Research direction
Start by locating the GooglePayButton component and its existing props, then inspect how its press and payment-processing states are handled. Define whether loading and loader are both required, implement the agreed loading behavior, and verify that the button prevents repeated taps while the custom or default indicator is displayed.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
I'm currently integrating the in a React Native app. One common UX expectation is to provide user feedback (like a loading spinner) while the payment flow is initiating or in progress.
Right now, there's no built-in support for a loading indicator or loader prop on the button, which results in either:
The user tapping multiple times
Manual handling outside the component
Describe the solution you'd like
It would be great if the component accepted a loader prop (boolean or custom component), allowing developers to:
Show a spinner or progress indicator on top of the button
Customize the loader style if needed
<GooglePayButton
loading={isProcessing}
loader={}
/>
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Wrapping in a parent View and overlaying a loader manually
Additional context
Add any other context or screenshots about the feature request here.
- Dominant language
- Kotlin
- Stars
- 63
- Forks
- 25
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Getting set up
- No Dockerfile or Docker Compose file
- No 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 google-pay/react-native-make-payment
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
google-pay/react-native-make-payment#103 · 1 reaction ·
All issues in google-pay/react-native-make-payment
Similar issues
-
submit-adaption submit-adaption-pre
Difficulty 1/5 Under an hour Newbie friendliness 82/100
BetterAndroid/android-notification-icon-project#750 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
openbase/planetsudo.engine#107 ·
Maintainers usually reply within 1 day
-
native-cpu: -Wreturn-type in skainet_row_threads.c:150 (worker fn has no return)Possibly taken @Doomguy-BFG9000 claimed this today. Opengood first issue size:xs skill:native
Difficulty 1/5 Under an hour Newbie friendliness 78/100
SKaiNET-developers/SKaiNET#1358 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
IBRAHIMDANS/i18nSupportPlus#577 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PostHog/posthog-kmp#100 ·
Maintainers usually reply within 2 days