-
Notifications
You must be signed in to change notification settings - Fork 426
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-9473: replaced parsys with container with responsive grid #1121
FORMS-9473: replaced parsys with container with responsive grid #1121
Conversation
jcr:primaryType="nt:unstructured" | ||
sling:resourceType="wcm/core/components/policies/mapping"/> | ||
jcr:title="Header" |
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.
do we really need title and layout in policies?
jcr:primaryType="nt:unstructured" | ||
sling:resourceType="wcm/foundation/components/responsivegrid"> | ||
jcr:title="Header" | ||
sling:resourceType="wcm/foundation/components/responsivegrid" |
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.
I might be missing something here, but what is the change done here? The resourceType still seems to be the same. Only the tag name is changed rom parsys1 to container1, does this even make any difference? I believe its just a name
57ac330
to
9d6eea3
Compare
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.
Container component should be replaced only for core component AF related artifacts.
- Blank AF v2 template
- AF Page V2 template type
Basic and Blank templates (Foundation AF component) shouldn't be changed.
cc : @sakshi-arora1
Description
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: