google-pay / google-pay/flutter-plugin
Handle configuration changes for the payment profile on the GooglePayButton widget
Open
Nobody has claimed this yet.
documentation
enhancement
- Dominant language
- Dart
- Stars
- 176
- Forks
- 147
- PR merge metrics
- No merged PRs in 30d
Description
The GooglePayButton widget receives payment configuration through a conceptually immutable parameter: it's recommended that the same configuration that checks whether a user is ready to pay is used to perform the actual payment.
Consider the following:
- Document the behavior of intentionally not updating the confguration if ia different asset or JSON string is added.
- Reject changes to the payment configuration through intentional exceptions or errors
Contributor 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.
Research direction
Start with the GooglePayButton widget and trace how its payment configuration is received and used across readiness checks and payment. Determine whether the intended outcome is documentation of unchanged configuration or rejection of changes; done requires an agreed behavior and corresponding verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter
- Domain
- mobile, payments
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100