Closed TalmizAhmed closed 3 months ago
~@rismehta I am aware that this is a backward incompatible change as the value of the tooltip and description is changing in the JSON. What version would I have to bump?~ Edit: N/A
Performance | Accessibility | Best-Practices | SEO | |
---|---|---|---|---|
Scores | 94 | 96 | 100 | 75 |
Performance | Accessibility | Best-Practices | SEO | |
---|---|---|---|---|
Scores | 100 | 96 | 100 | 75 |
Id | Impact |
---|---|
label-title-only | serious |
target-size | serious |
Id | Impact |
---|---|
label-title-only | serious |
target-size | serious |
Id | Impact |
---|---|
label-title-only | serious |
target-size | serious |
Performance | Accessibility | Best-Practices | SEO | |
---|---|---|---|---|
Scores | 100 | 96 | 100 | 75 |
Performance | Accessibility | Best-Practices | SEO | |
---|---|---|---|---|
Scores | 93 | 96 | 100 | 75 |
Id | Impact |
---|---|
label-title-only | serious |
target-size | serious |
Id | Impact |
---|---|
label-title-only | serious |
target-size | serious |
Id | Impact |
---|---|
label-title-only | serious |
target-size | serious |
Attention: Patch coverage is 83.33333%
with 1 line
in your changes missing coverage. Please review.
Project coverage is 81.48%. Comparing base (
76c66be
) to head (60be082
).
Files | Patch % | Lines |
---|---|---|
...ponents/internal/form/FormStructureParserImpl.java | 83.33% | 0 Missing and 1 partial :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Performance | Accessibility | Best-Practices | SEO | |
---|---|---|---|---|
Scores | 93 | 96 | 100 | 75 |
Performance | Accessibility | Best-Practices | SEO | |
---|---|---|---|---|
Scores | 100 | 96 | 100 | 75 |
Id | Impact |
---|---|
label-title-only | serious |
target-size | serious |
Id | Impact |
---|---|
label-title-only | serious |
target-size | serious |
Id | Impact |
---|---|
label-title-only | serious |
target-size | serious |
Performance | Accessibility | Best-Practices | SEO | |
---|---|---|---|---|
Scores | 100 | 96 | 100 | 75 |
Performance | Accessibility | Best-Practices | SEO | |
---|---|---|---|---|
Scores | 94 | 96 | 100 | 75 |
Id | Impact |
---|---|
label-title-only | serious |
target-size | serious |
Id | Impact |
---|---|
label-title-only | serious |
target-size | serious |
Id | Impact |
---|---|
label-title-only | serious |
target-size | serious |
Performance | Accessibility | Best-Practices | SEO | |
---|---|---|---|---|
Scores | 100 | 96 | 100 | 75 |
Performance | Accessibility | Best-Practices | SEO | |
---|---|---|---|---|
Scores | 92 | 96 | 100 | 75 |
Id | Impact |
---|---|
label-title-only | serious |
target-size | serious |
Id | Impact |
---|---|
label-title-only | serious |
target-size | serious |
Id | Impact |
---|---|
label-title-only | serious |
target-size | serious |
Description
UE allows rich text to be added in these fields, and since they will contain HTML tags, the form json embedded in the code tags is split by the tags present inside these fields and causes the eds rendition of the form to break when they are not encoded properly
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: