"Disconnect" reusable component instance to break it up again

Suggestions/Ideas
1

Reusable components are great… but once a component is reusable, it cannot be re-used as the basis for some other new component. For example, creating a modal template with a set of containers, blocks, buttons, etc cannot be used as a template for other modals… because one cannot put new components inside of a reusable component without affecting all instances of that reusable component. So to make a new modal with different content, we have to re-create the modal template from scratch (since there is no copy/paste for components across pages). So, a feature which which would be super useful:

An option to take the instance of a reusable component and make it not be a reusable component anymore. That is to say, break it up again into it’s individual components, doing the opposite of what the “make reusable” button does.

1 Like
2

Thank you for this feedback. An internal ticket has been created BKNDLSS-31091. We will research this.

Best Regards, Nikita.

3

Hello, I just want to add my five cents that this will indeed be very useul for me. In fact I realised that this would have saved me a tremendous amount of copy & paste time.

A particular usecase is that I often create styled components like a panel, with close buttons etc. Or a a generic lists with certain common pieces, like arrows, hover styling, etc. But then the exact content inside I might want to change depending on the page.

It’s something that I find useful not only within one app, but also across multiple apps that I work on.