-
Notifications
You must be signed in to change notification settings - Fork 44
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
Encode formDefinition with jsonString context #1242
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## dev #1242 +/- ##
=========================================
Coverage 81.41% 81.41%
Complexity 818 818
=========================================
Files 94 94
Lines 2201 2201
Branches 301 301
=========================================
Hits 1792 1792
Misses 252 252
Partials 157 157 ☔ View full report in Codecov by Sentry. |
Lighthouse scores (desktop)
|
Lighthouse scores (mobile)
|
Accessibility Violations Found
|
3 similar comments
Accessibility Violations Found
|
Accessibility Violations Found
|
Accessibility Violations Found
|
Support for jsonString context is now available in public AEM cloud release Release 16357 |
What is the behavior of the code if context is not available ? Is the rendering blocked |
@rismehta No the rendering would just be in the default context of the html tag, without the encoding provided by jsonString |
@rismehta This test case will be improved by @deepprakash345 to include checks for this use case too and is being tracked by a separate ticket (FORMS-14628) |
d755a7d
to
3e1d92e
Compare
Lighthouse scores (mobile)
|
Lighthouse scores (desktop)
|
Accessibility Violations Found
|
2 similar comments
Accessibility Violations Found
|
Accessibility Violations Found
|
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.
please add test case
…a test case to check the json emitted in case of eds servlet originated request
…ore-forms-components into eds-encoding-support
…a test case to check the json emitted in case of eds servlet originated request
0491f05
to
34862cf
Compare
…a test case to check the json emitted in case of eds servlet originated request
Lighthouse scores (mobile)
|
Lighthouse scores (desktop)
|
Accessibility Violations Found
|
4 similar comments
Accessibility Violations Found
|
Accessibility Violations Found
|
Accessibility Violations Found
|
Accessibility Violations Found
|
Lighthouse scores (mobile)
|
Lighthouse scores (desktop)
|
Accessibility Violations Found
|
…a test case to check the json emitted in case of eds servlet originated request
…a test case to check the json emitted in case of eds servlet originated request
Lighthouse scores (mobile)
|
Lighthouse scores (desktop)
|
Accessibility Violations Found
|
2 similar comments
Accessibility Violations Found
|
Accessibility Violations Found
|
* Encode formDefinition with jsonString context * Encode formDefinition with jsonString context * updated the proxy component to point to v2 version of page and wrote a test case to check the json emitted in case of eds servlet originated request * Encode formDefinition with jsonString context * updated the proxy component to point to v2 version of page and wrote a test case to check the json emitted in case of eds servlet originated request * updated the proxy component to point to v2 version of page and wrote a test case to check the json emitted in case of eds servlet originated request * updated the proxy component to point to v2 version of page and wrote a test case to check the json emitted in case of eds servlet originated request --------- Co-authored-by: Deep Prakash Dewanji <deepprakashdewanji@labusers-mbp-9.corp.adobe.com>
Description
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: