feat(modal-checkout): custom coupon form

[miguelpeixe]

All Submissions:

• Have you followed the Newspack Contributing guideline?
• Does your code follow the WordPress' coding standards and VIP Go coding standards?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Changes proposed in this Pull Request:

Requires #1602.

Implements a custom coupon form handling so it doesn't inherit Woo's default UI handling of the form. The custom handling is implemented by changing the class name of the form.

How to test the changes in this Pull Request:

1. Check out this branch and make sure you have coupons enabled and at least 1 enabled coupon code
2. Go through the modal checkout flow through a Checkout Button block (make sure it's not a donation product, which has coupons disabled)
3. Enter an invalid coupon code and confirm you get the error message as above and the input is focused
4. Enter a valid coupon code and confirm the checkout is updated to include the discount
5. Click to remove the coupon code in the order review table and confirm the coupon is removed and the coupon form input is focused

Other information:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your changes, as applicable?
• Have you successfully ran tests with your changes locally?

[leogermani]

:chefkiss:

Do you think it's ok to modify the class name and potentially lose support for other plugins customizations on this form? I think it's fine, just confirming

[miguelpeixe]

Do you think it's ok to modify the class name and potentially lose support for other plugins customizations on this form? I think it's fine, just confirming

It's something to keep an eye out for. I'm not aware of plugins that replace the coupon behavior.

It's worth noting that the code that this takes inspiration from, to be as close to the original behavior as possible, is 9 years old and is not exactly "hookable" to be extended. We'd be using such a hook if there was any 😅 . So I'd say it's safe to assume it shouldn't conflict with anything.

[matticbot]

🎉 This PR is included in version 3.0.0-epic-ras-acc.1 🎉

The release is available on:

• npm package (@epic/ras-acc dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[matticbot]

🎉 This PR is included in version 3.1.0-epic-ras-acc.1 🎉

The release is available on:

• npm package (@epic/ras-acc dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[matticbot]

🎉 This PR is included in version 3.2.0-epic-ras-acc.1 🎉

The release is available on:

• npm package (@epic/ras-acc dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[matticbot]

🎉 This PR is included in version 3.3.0-epic-ras-acc.1 🎉

The release is available on:

• npm package (@epic/ras-acc dist-tag)
• GitHub release

Your semantic-release bot 📦🚀