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.

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

feat(payment): PAYPAL-5213 added messages implementation to Braintree PayPal Credit button strategy #2801

Merged
merged 1 commit into from
Mar 6, 2025

Conversation

serhii-tkachenko
Copy link
Contributor

@serhii-tkachenko serhii-tkachenko commented Mar 5, 2025

What?

Added messages implementation to Braintree PayPal Credit button strategy

Why?

Braintree Messaging is available only when Braintree PayPal Credit is enabled, so the best place to hold this implementation is in Braintree PayPal Credit Button strategy to render banner on cart page. So as part one of messages implementation migration the implementation was duplicated from Braintree PayPal to Braintree PayPal Credit button strategy

Testing / Proof

Unit tests
Manual tests
CI

US VPN location:
Screenshot 2025-03-06 at 10 32 18

Non US VPN location:
Screenshot 2025-03-06 at 10 32 34

@serhii-tkachenko serhii-tkachenko marked this pull request as ready for review March 6, 2025 08:36
@serhii-tkachenko serhii-tkachenko requested a review from a team as a code owner March 6, 2025 08:36
@serhii-tkachenko serhii-tkachenko changed the title feat(payment): PAYPAL-5213 moved messages implementation from Braintree PayPal to Braintree PayPal Credit button strategy feat(payment): PAYPAL-5213 added messages implementation to Braintree PayPal Credit button strategy Mar 6, 2025
@serhii-tkachenko serhii-tkachenko merged commit 3c7f14f into bigcommerce:master Mar 6, 2025
5 checks passed
@serhii-tkachenko serhii-tkachenko deleted the PAYPAL-5213 branch March 6, 2025 09:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants