Notify users about unavailable linter in the linter widget
requested to merge 346038-notify-users-about-unavailable-linter-in-the-linter-widget-instead-of-a-500-error-alert into master
What does this MR do and why?
In pipeline editor, when the Linter API returns an error, we cannot validate CI configurations, show the visualization or the merged YAML. So we now have an improved experience that handles that state. This means:
- The validation widget has a special state for when it cannot give an answer to: Is this valid?
- All tabs except the edit one will have a generic error message
Screenshots or screen recordings
Before | After |
---|---|
Screen_Recording_2021-12-16_at_5.30.04_PM | Screen_Recording_2021-12-16_at_2.08.28_PM |
How to set up and validate locally
- Go to
CI/CD
=>Editor
- Since you cannot trigger a 500 error in the UX (which is a good thing!) you can comment out one of the variables in the
ciConfigData
query - Refresh the page
- Notice how the validation segment (the linter widget) now shows a new error message
- Check each tab and ensure the messages are accurate
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.
Related to #346038 (closed)
Edited by Frédéric Caplette