AEM Pattern Detector Interpretation | Community
Skip to main content
Level 2
June 20, 2019
Solved

AEM Pattern Detector Interpretation

  • June 20, 2019
  • 11 replies
  • 26359 views

Hi all

We're analyzing the output of the Pattern Detector and some of the violations seems strange.

1. Non-Backwards Compatible Changes

For instance, we getting:

The content stored at /apps/<...>/cq:dialog/content/items/section3/items/column/items/details-group/items/details by including (sling:resourceType) the JCR path at /libs/cq/gui/components/authoring/dialog/richtext might be incompatible after update and might need some adaption

We would like to learn more about the severity of this issue, like what type of change is expected? Is there a backward compatible alternative for richtext, for instance?

2. Content Area Violation

For instance, we getting:

The content stored at /apps/<...> by overriding (sling:superResourceType) the JCR path at /libs/cq/workflow/components/model/process might be incompatible after update and might need some adaption

However /libs/cq/workflow/components/model/processis is explicitly marked as granite:PublicArea which is safe for that type of actions.

If anyone has answers, please share.

Thanks in advance!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

If the documentation does not provide actionable information how you can handle these, I would recommend you to open a support ticket and ask for advice.

Unfortunately I don't have first-hand experience with it yet, so I cannot help you in that area :-/

Jörg

11 replies

Level 3
October 15, 2020
i have tried to "copy and past" the core component "/apps/core/wcm/components/text/v2/text" and the issue is highlighted also on core component "clone":