feat: added text overrides on StripePaymentCheckoutAction

[HarisSpahijaPon]

Signed-off-by: Haris Spahija [email protected]

Part of: #409
Impact: minor
Type: feature

Component

StripePaymentCheckoutAction now has overrides when i18next will be implemented (see #409)

Breaking changes

No breaking chances, all added fields are optional

Testing

1. Add a new prop billingAddressTitleText to <StripePaymentCheckoutAction />
2. Add the value "test" to billingAddressTitleText
3. Button should display "test" when test is given as a value to the prop. When the prop billingAddressTitleText is not added, it should default to the values given in default props

Added props:

billingAddressTitleText: PropTypes.string,
secureCaptionText: PropTypes.string,

[HarisSpahijaPon]

@aldeed these items should be translated aswell but are they part of the component? Should I add overrides in the same way?

const billingAddressOptions = [{
  id: "1",
  label: "Same as shipping address",
  value: "same_as_shipping"
},
{
  id: "2",
  label: "Use a different billing address",
  value: "use_different_billing_address"
}];

[aldeed]

@HarisSpahijaPon Yes, I would move it down into the component and add sameAddressLabelText and differentAddressLabelText props or something similar.

[rc-publisher]

🚀 Preview deployed

Built with commit 1aef6f5

https://deploy-preview-461--stoic-hodgkin-c0179e.netlify.com

[aldeed]

Need to deal with billingAddressOptions as discussed above

[HarisSpahijaPon]

I currently have very little time to do this one, I opened it to the community in the story. Maybe someone can fix this for a new release.

[aldeed]

It works as is and billingAddressOptions can be done in a future PR

[rc-publisher]

🎉 This PR is included in version 0.69.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀