Closed davidjgonzalez closed 7 years ago
If versioning of editor clientlibs is the correct approach, there is the downstream concern of multi-tenant scenarios where AEM "Tenant A" is using v1 and Tenant V is using v2; what is the pattern for loading the correct editor clientlib based on the Tenant?
I think the right approach here at least for CSS is to always reference selectors with a version in it. That way two different versions don't overlap. For JavaScript there is no simple solution though.
@davidjgonzalez Maybe we can add to the documentation that, in case of overriding with sling:resourceSuperType, also the extraClientlibs property has to be overridden, so that it points to the correct version?
The editor clientlibs categories [1] are not versioned; they are explicitly made part of
cq.author.editor
to be automatically pulled into the AEM authoring editors UIs.The issue comes arises in v2, when the editor clientlibs deviates from v1; in this scenario, both clientlibs will be loaded to unknown effect.
Oddly, the image component's editor category is versioned (
core.wcm.components.image.v1.editor
)Unversioned editor clientlibs (
cq.authoring.dialog
)