Handle payment-related errors at the parent component level
What does this MR do and why?
Describe in detail what your merge request does and why.
This MR is a quick follow-up on !107909 (merged). It aims to handle payment method related errors at the parent component level for the Add-ons Purchase flow. The MR is tiny for iteration reasons. Another reason is that I thought of an approach that turned out to be too complex.
Relates to #386772 (closed)
The MR is just refactoring and contains no visual changes.
| Title | MR |
|---|---|
| Handle all page-level errors at the parent component level (Add-ons flow) | !107909 (merged) |
| Handle all page-level errors at the parent component level (subscription flow) | !108190 (merged) |
| Handle payment-related errors at the parent component level |
|
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Angelo Gulina