I was able to get this feature working in a proxy component (custom
component that extends the core component via resourceSuperType). I was
using Tabs, but it could be done the same way with Carousel. The key is
to define the markup selectors correctly in the clientlib file that gets
executed on editor instantiation.../* * Copy this to your proxy
component, rather than allowing Sling Resource Merger to use the core
component's version...
/apps/core/wcm/components/tabs/v1/tabs/clientlibs/editorho...
This worked for me! The essentials in my implementation
were:custom-event-polyfillreact-app-polyfill/ie11react-app-polyfill/stableI
was able to install each module via NPM and import them atop my index.js
file of the react app, and IE 11 now has all of the polyfills needed to
successfully run my react app. Thanks for the share, michaelr87730166!
I'm facing a very similar issue:`unhandled promise rejection TypeError:
Object doesn't support this action `I have followed the polyfill
instructions, but can't seem to figure this one out... any suggestions,
anyone?
Hi all,I'm using SPA SDK and adding custom React components to my pages.
That's going great. I would like to know, has anyone successfully found
a way to implement a layout container inside of a React component? I'm
reading through the API @adobe/cq-react-editable-components - npm but
not finding it incredibly helpful with this particular situation.Thanks
in advance for any help!
I know the Style System is relatively new to AEM. Are the styles from
the component-level policy exposed in some way, or do you know some way
to access those properties via Sling Model so I can expose them in the
JSON and read them with React? I appreciate your help. Running AEM 6.5
with SPA Archetype and React.
