-
-
Notifications
You must be signed in to change notification settings - Fork 9.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: support display HTML format in API error responses #7127
feat: support display HTML format in API error responses #7127
Conversation
Signed-off-by: Ryan Wang <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #7127 +/- ##
============================================
+ Coverage 56.99% 57.19% +0.20%
- Complexity 3999 4047 +48
============================================
Files 714 719 +5
Lines 24110 24352 +242
Branches 1585 1598 +13
============================================
+ Hits 13742 13929 +187
- Misses 9756 9805 +49
- Partials 612 618 +6 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Quality Gate passedIssues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JohnNiang The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
/area ui
/milestone 2.20.x
What this PR does / why we need it:
Add supports for display HTML format in API error responses
See #7115
Examples:
Which issue(s) this PR fixes:
Fixes #7115
Special notes for your reviewer:
Nginx mock example:
Does this PR introduce a user-facing change?