Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix storedPaymentMethodId parameter on the onDisableStoredPaymentMethod Drop-in event #504

Merged
merged 1 commit into from Nov 12, 2020
Merged

Fix storedPaymentMethodId parameter on the onDisableStoredPaymentMethod Drop-in event #504

merged 1 commit into from Nov 12, 2020

Conversation

marcperez
Copy link
Member

@marcperez marcperez commented Nov 12, 2020 •
edited

Summary

The Drop-in onDisableStoredPaymentMethod event now passes the correct storedPaymentMethodId parameter.

onDisableStoredPaymentMethod: (storedPaymentMethodId, resolve, reject) => {

}

@sonarcloud
Copy link

sonarcloud bot commented Nov 12, 2020

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@github-actions
Copy link
Contributor

Size Change: +11 B (0%)

Total Size: 124 kB

Filename Size Change
packages/lib/dist/adyen.js 124 kB +11 B (0%)

compressed-size-action

@marcperez marcperez merged commit 6409c74 into master Nov 12, 2020
@marcperez marcperez deleted the fix/onDisableStoredPaymentMethod-storedPaymentMethodId branch November 12, 2020 14:16
@marcperez marcperez mentioned this pull request Dec 14, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@sponglord sponglord sponglord approved these changes

@pabloai pabloai Awaiting requested review from pabloai

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@marcperez @sponglord