Is it possible to create a Super-component (like a new type of core-component)... so I don't need to map my Angular-custom-component to an existing AEM Core Component... but instead map it to a new super-component that I create?
The reason for the question is that if I map my angular-custom-component to a pre-existing aem-core-component, the system overwrites that aem-component inside the SPA Editor... which is something I don't want. Also, I want to be able to configure the modal window that opens when we need to edit the custom component. If I map to a pre-existing core-component, like the text component, for example, the edit-dialog will have the properties for that text component. But if I am able to create my own super-component, I would probably be able to edit the dialog-window that will show when I edit that custom-component inside the SPA editor.
Yeah, that page talks about it, for sure. Thank you! 😃 It, however, explores a multi-step Java solution, which seems very time-consuming and doesn't really answer some of the core issues. I will have a meeting this week with an Adobe team specialized on the SPA-Editor and will post the best solution as a comment here as soon as I get the answer.