You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TagManager automatically resolves the cq:movedTo property when fetching cq:tags of a resource. This resolution also happens when calling adapTo(Tag.class) on any resource that has such a property, returning the successor tag.
I originally wanted to implement mergeTag() and moveTag() as well, but basically hit a wall when considering this operations does not only shuffle individual tags around, but also handles whole subtrees of tags and creates copies and movedTo / backlinks relationships between them.
The text was updated successfully, but these errors were encountered:
dennisfisch
added a commit
to dennisfisch/io.wcm.testing.aem-mock
that referenced
this issue
Oct 25, 2024
TagManager automatically resolves the cq:movedTo property when fetching cq:tags of a resource. This resolution also happens when calling adapTo(Tag.class) on any resource that has such a property, returning the successor tag.
I originally wanted to implement mergeTag() and moveTag() as well, but basically hit a wall when considering this operations does not only shuffle individual tags around, but also handles whole subtrees of tags and creates copies and movedTo / backlinks relationships between them.
The text was updated successfully, but these errors were encountered: