Include Forms and CIF add-on in the classification map#40
Conversation
|
@royteeuwen WDYT? |
Add info on incorrect classification for forms components
kwin
force-pushed
the
feature/map-with-cif-form-addon
branch
from
9299456 to
78e2f93
Compare
|
| /libs/fd/af/authoring/components/granite/drawer,INTERNAL | ||
| /libs/fd/af/authoring/components/granite/form/afImageStyleSelect,INTERNAL | ||
| /libs/fd/af/authoring/components/granite/form/autocomplete,INTERNAL | ||
| /libs/fd/af/authoring/components/granite/form/bindrefselector,FINAL |
There was a problem hiding this comment.
Wasn't this the one you were stumbling on @royteeuwen? Seems the classification has been fixed (at least with the AEMaaCS add-on).
There was a problem hiding this comment.
Indeed, sadly enough not for aem 6.5.23 / aem 6.6.1 :(... still in InternalArea there...
There was a problem hiding this comment.
At least for 6.6.1 this is not true, once you install the Forms add-on it is FINAL as well. I just released it for 6.6.1 (https://central.sonatype.com/artifact/biz.netcentric.filevault.validator.maps/aem-classification-map-repo-annotations/6.6.1.0)
| `/libs/cq/dtm-reactor/components/conf/page` | `granite:InternalArea` (via parent) | Launch Cloud Configurations use that artificial resource type | 6.5.3, 6.5.13, 2020.3.2483, 2021.6.5586, 2022.7.8085, 2024.10.18099, 2025.11.234821 | - | ||
| `/libs/cq/workflow/components/pages/model` | `granite:InternalArea` | Workflow Models | 6.5.x, All AEMaaCS versions | https://daycare.day.com/content/home/netcentric/netcentric_de/aemasacloudservice/208727.html (CQ-4291242) | ||
| `/libs/cq/dtm-reactor/components/conf/page` | `granite:InternalArea` (via parent) | Launch Cloud Configurations use that artificial resource type | 6.5.x, All AEMaaCS versions | - | ||
| `/libs/fd/af/authoring/components/granite` | `granite:InternalArea` | Forms Datasources or Components | 6.5.x, All AEMaaCS versions | [AEM Core Forms Components, Issue 1775](https://github.com/adobe/aem-core-forms-components/issues/1775) |
There was a problem hiding this comment.
I guess that this might then not be the case for AEMaaCS version. If you do have an export for AEM 6.5 / 6.6 then I can validate for other resource types as well
There was a problem hiding this comment.
I now removed this, as once you install the add-on it has the correct classification AFAICT.
very nice :)! Another validation automated ;) |
2 participants
Add info on incorrect classification for forms components