Skip to content

Add dictionary to map system to friendly errors for purchase flows

What does this MR do and why?

Describe in detail what your merge request does and why.

To tackle &9543 (closed) – and issue: #386710 (closed) – this MR introduces:

  1. a dictionary that helps mapping systems or unfriendly errors to (more) friendly ones
  2. a bit of logic to help the mapping be more resilient
  3. a component, wrapping a GlAlert, dedicated to the Purchase flow to display help with error displaying

(The original idea was to use a Mixin or introduce a new error handling component, the ErrorBoundary. The approach in this MR seems to be more MVC. Additionally, given errors contain links, we can use the safe-html directive only in one place)

Note that the system will be actually introduced with #386723 (closed) – this MR introduces no visual changes.

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.

Edited by Angelo Gulina

Merge request reports