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

FORMS-13935 update examples for aemcomponents.dev #1204

Merged
merged 1 commit into from Apr 29, 2024

Conversation

barshat7
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.

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

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

@barshat7 barshat7 force-pushed the FORMS-13935-aemcomponents_dev branch from 17ed8d5 to e2c0985 Compare April 23, 2024 09:49
@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

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

FORMS-13935 update examples for aemcomponents.dev

FORMS-13935 update examples for aemcomponents.dev
@barshat7 barshat7 force-pushed the FORMS-13935-aemcomponents_dev branch from e2c0985 to 482d2e1 Compare April 23, 2024 12:48
@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 94 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

codecov bot commented Apr 23, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.81%. Comparing base (4d09843) to head (482d2e1).

Additional details and impacted files
@@            Coverage Diff            @@
##                dev    #1204   +/-   ##
=========================================
  Coverage     80.81%   80.81%           
  Complexity      782      782           
=========================================
  Files            91       91           
  Lines          2116     2116           
  Branches        286      286           
=========================================
  Hits           1710     1710           
  Misses          252      252           
  Partials        154      154           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

<filter root="/content/forms/af/core-forms-components-examples/sample" mode="merge"/>
<filter root="/content/dam/formsanddocuments/core-forms-components-examples/sample" mode="merge"/>
<filter root="/content/forms/af/core-forms-components-examples/test-fragment" mode="merge"/>
<filter root="/content/dam/formsanddocuments/core-forms-components-examples/test-fragment" mode="merge"/>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks incorrect to me. The whole point of aemcomponents.dev is to describe components. The page used in the examples is always a SITE page.

While I agree that fragment have a requiremenet to be under /content/forms/af, the sample page used is incorrect. Please refer on how text input is demonstrated and try using a fragment inside an existing SITES page, let's not create a PAGE inside /content/forms/af

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The page use for fragment and embed both are SITE pages . e.g. examples/ui.content/src/main/content/jcr_root/content/core-components-examples/library/adaptive-form/fragment/.content.xml
But since we need to embed an adaptive form & an adaptive form fragment in these SITE pages, so the adaptive form and fragment are placed under /content/forms/af

The text input use case is not relevant here because text input is just a component under a form container in a SITE page. Here these are embed components which need a reference to an adaptive form.

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.

check comments

@rismehta rismehta merged commit ef7330d into dev Apr 29, 2024
11 checks passed
@rismehta rismehta deleted the FORMS-13935-aemcomponents_dev branch April 29, 2024 08:11
github-actions bot pushed a commit that referenced this pull request May 3, 2024
FORMS-13935 update examples for aemcomponents.dev

FORMS-13935 update examples for aemcomponents.dev
github-actions bot pushed a commit that referenced this pull request May 7, 2024
FORMS-13935 update examples for aemcomponents.dev

FORMS-13935 update examples for aemcomponents.dev
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