Our project’s ui.frontend is rendering our clientlib-site with some ES6 arrow notations. I verified that the arrow notations occur in the dist clientlib-site js file. Not converting ES6 to ES5 causes our site to fail in IE11, which only supports up to ES5. Our tsconfig.json is already set to compile...

I've opened an Adobe support ticket on this since there has not been any significant movement.

I've seen several posts/questions around this topic, but never a clear answer. Here is a Git issue that describes it quite well:https://github.com/adobe/aem-core-wcm-components/issues/421 I am currently on AEM 6.5.6 and Core Components 2.11.0 and the issue is still able to be replicated. I attempted...

Thank you!!

Understood. Is there anywhere that has the full profile code? In the documentation, it provides some of it, but not all. There is a '...' which I assume contains collapsed code. An additional Maven profile, named classic has been added to modify the build to target AEM 6.x environments: <!-- AEM 6....

I am trying to deploy an SPA to AEM version 6.5.5 using the -Pclassic build profile, but at the end of the build process, I receive the following warning: [WARNING] The requested profile "classic" could not be activated because it does not exist.Am I missing something in order to include that profil...

I am attempted to map the Title component in an SPA, but was curious how others were able to map the "type" property to the title.component.html file. title.component.tsimport { Component, Input, OnInit } from '@angular/core'; import {MapTo} from '@adobe/cq-angular-editable-components'; @Component(...

This is more of a feature request type post, but would be curious if there are any thoughts around its feasibility currently. In an effort to reduce the number of components made available to content producers, we're creating style systems that apply the look/feel of the component. In doing so, howe...

Right, but what you can do is select the Adobe Core 'Container' component as the 'Slide' of your carousel. Doing so would allow you to place any number of other components in that 'Slide', such as 3 Image components, and those could be resized using the layout editor of the Container.

Just curious, but have you considered having a 'Container' component be the 'Slide', and then you can place 3 Image components within each slides' container? That way you would only have 2 panels, but would still be able to manage/configure the images individually.