Skip to content
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

Merged
merged 10 commits into from
Jun 5, 2024
Merged

Conversation

TalmizAhmed
Copy link
Contributor

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • I have signed the Adobe Open Source CLA.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes and the overall coverage did not decrease.
  • All unit tests pass on CircleCi.
  • I ran all tests locally and they pass.

@TalmizAhmed TalmizAhmed marked this pull request as draft May 17, 2024 11:24
@TalmizAhmed TalmizAhmed changed the title Encode formDefinition with jsonString context [DELAY MERGE] - Encode formDefinition with jsonString context May 17, 2024
Copy link

codecov bot commented May 17, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.41%. Comparing base (e0481b5) to head (a156b7b).

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.
📢 Have feedback on the report? Share it here.

@adobe-bot
Copy link

Lighthouse scores (desktop)

Performance Accessibility Best-Practices SEO
Scores 100 96 100 75

@adobe-bot
Copy link

Lighthouse scores (mobile)

Performance Accessibility Best-Practices SEO
Scores 93 96 100 75

@adobe-bot
Copy link

Accessibility Violations Found

Id Impact
label-title-only serious
landmark-one-main moderate
region moderate
target-size serious

3 similar comments
@adobe-bot
Copy link

Accessibility Violations Found

Id Impact
label-title-only serious
landmark-one-main moderate
region moderate
target-size serious

@adobe-bot
Copy link

Accessibility Violations Found

Id Impact
label-title-only serious
landmark-one-main moderate
region moderate
target-size serious

@adobe-bot
Copy link

Accessibility Violations Found

Id Impact
label-title-only serious
landmark-one-main moderate
region moderate
target-size serious

@TalmizAhmed TalmizAhmed marked this pull request as ready for review May 23, 2024 09:25
@TalmizAhmed TalmizAhmed changed the title [DELAY MERGE] - Encode formDefinition with jsonString context Encode formDefinition with jsonString context May 23, 2024
@TalmizAhmed
Copy link
Contributor Author

TalmizAhmed commented May 23, 2024

Support for jsonString context is now available in public AEM cloud release Release 16357
cc: @rismehta

@rismehta
Copy link
Collaborator

Support for jsonString context is now available in public AEM cloud release Release 16357
cc: @rismehta

What is the behavior of the code if context is not available ? Is the rendering blocked

@TalmizAhmed
Copy link
Contributor Author

@rismehta No the rendering would just be in the default context of the html tag, without the encoding provided by jsonString

@TalmizAhmed
Copy link
Contributor Author

@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)

@adobe-bot
Copy link

Lighthouse scores (mobile)

Performance Accessibility Best-Practices SEO
Scores 93 96 100 75

@adobe-bot
Copy link

Lighthouse scores (desktop)

Performance Accessibility Best-Practices SEO
Scores 100 96 100 75

@adobe-bot
Copy link

Accessibility Violations Found

Id Impact
label-title-only serious
landmark-one-main moderate
region moderate
target-size serious

2 similar comments
@adobe-bot
Copy link

Accessibility Violations Found

Id Impact
label-title-only serious
landmark-one-main moderate
region moderate
target-size serious

@adobe-bot
Copy link

Accessibility Violations Found

Id Impact
label-title-only serious
landmark-one-main moderate
region moderate
target-size serious

Copy link
Collaborator

@rismehta rismehta left a 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

Deep Prakash Dewanji added 2 commits June 5, 2024 10:04
…a test case to check the json emitted in case of eds servlet originated request
TalmizAhmed and others added 2 commits June 5, 2024 04:34
…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
@adobe-bot
Copy link

Lighthouse scores (mobile)

Performance Accessibility Best-Practices SEO
Scores 94 96 100 75

@adobe-bot
Copy link

Lighthouse scores (desktop)

Performance Accessibility Best-Practices SEO
Scores 100 96 100 75

@adobe-bot
Copy link

Accessibility Violations Found

Id Impact
label-title-only serious
target-size serious

4 similar comments
@adobe-bot
Copy link

Accessibility Violations Found

Id Impact
label-title-only serious
target-size serious

@adobe-bot
Copy link

Accessibility Violations Found

Id Impact
label-title-only serious
target-size serious

@adobe-bot
Copy link

Accessibility Violations Found

Id Impact
label-title-only serious
target-size serious

@adobe-bot
Copy link

Accessibility Violations Found

Id Impact
label-title-only serious
target-size serious

@adobe-bot
Copy link

Lighthouse scores (mobile)

Performance Accessibility Best-Practices SEO
Scores 94 96 100 75

@adobe-bot
Copy link

Lighthouse scores (desktop)

Performance Accessibility Best-Practices SEO
Scores 100 96 100 75

@adobe-bot
Copy link

Accessibility Violations Found

Id Impact
label-title-only serious
target-size serious

Deep Prakash Dewanji added 2 commits June 5, 2024 13:13
…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
@adobe-bot
Copy link

Lighthouse scores (mobile)

Performance Accessibility Best-Practices SEO
Scores 93 96 100 75

@adobe-bot
Copy link

Lighthouse scores (desktop)

Performance Accessibility Best-Practices SEO
Scores 100 96 100 75

@adobe-bot
Copy link

Accessibility Violations Found

Id Impact
label-title-only serious
target-size serious

2 similar comments
@adobe-bot
Copy link

Accessibility Violations Found

Id Impact
label-title-only serious
target-size serious

@adobe-bot
Copy link

Accessibility Violations Found

Id Impact
label-title-only serious
target-size serious

@rismehta rismehta merged commit 4a55a33 into dev Jun 5, 2024
9 of 10 checks passed
@rismehta rismehta deleted the eds-encoding-support branch June 5, 2024 09:23
github-actions bot pushed a commit that referenced this pull request Jun 6, 2024
* 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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants