We're extending our application to SPA support, which means all the Touch UI components are extended to SPA and writing the code in Angular.
As mentioned, all the components, which support SPA that would work in the SPA template. There is a reference Touch UI component, which would refer to other AEM components from another AEM page. The logic of the reference touch UI component would be to get the path of the AEM page and add in the sling: include. How can this logic be handled if we convert this into a SPA reference component (angular)?
I'm raising this as the sling: include can't be handled it in angular component, how to handled this?
Your help would be pretty much appreciated.
Solved! Go to Solution.
Thanks for the response @HImanshu_Jain_ .
We are using AEM 6.5.10. However, the reference which I mentioned above, it's our custom component. This was provided to our customers in classic UI. Even in the touch UI, it works fine. We are in a situation to give the feature in SPA as well, as most of the pages use this component. do we have any solution for this?
I just want to check, would the "data-CQ-data-path" angular directive resolve the issue? I was studying a few Adobe SPA components and I came across this