[x] AEM Version, including Service Packs, Cumulative Fix Packs, etc: 6.4+
[x] ACS AEM Commons Version: ASAP
[x] Reproducible on Latest? n/a
Expected Behavior
When a project enables a coral-ui-aem64 or coral-ui-aem65 checklist, and whose package involves nodes under /apps/ with coral ui sling:resourceType or sling:resourceSuperType values, including granite and cq foundation form fields, the oakpal:scan goal should identify the following as violations:
Missing required properties
Incorrect type for known properties, optional or required.
Container/Collection elements missing an items node or a datasource node
(Bonus) configurable requirements for i18n / accessibility details, like enforcing that all fieldLabels and fieldDescriptions are populated, and whatever else we can come up with.
(Bonus Bonus) Configure your own validators for custom dialog fields and coral UI elements using gnd.
It's practically the wild west right now with all these component generators and dialog resource providers and things and who even knows what a valid coral UI structure is supposed to look like at the end of the day, amirite?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Required Information
Expected Behavior
When a project enables a
coral-ui-aem64
orcoral-ui-aem65
checklist, and whose package involves nodes under/apps/
with coral uisling:resourceType
orsling:resourceSuperType
values, including granite and cq foundation form fields, the oakpal:scan goal should identify the following as violations:items
node or a datasource nodegnd
... gnd:servercomponent
and.. gnd:gnd
sections to generate the element validator classes. See theShow Source
link on each page to get the underlying sphinx text: https://helpx.adobe.com/experience-manager/6-5/sites/developing/using/reference-materials/granite-ui/api/_sources/jcr_root/libs/granite/ui/components/coral/foundation/form/multifield/index.rst.txtActual Behavior
It's practically the wild west right now with all these component generators and dialog resource providers and things and who even knows what a valid coral UI structure is supposed to look like at the end of the day, amirite?
Links
Read this site for the overview of coral UI: 6.5: https://helpx.adobe.com/experience-manager/6-5/sites/developing/using/reference-materials/granite-ui/api/jcr_root/libs/granite/ui/index.html 6.4: https://helpx.adobe.com/experience-manager/6-4/sites/developing/using/reference-materials/granite-ui/api/jcr_root/libs/granite/ui/index.html