Hey there! Just wanted to clarify that what you're experiencing is actually a feature, not a bug, of the Blocklet Platform. Composability is super important to us, so when you're putting blocklets together, there are dependency relationships between them. Basically, if blocklet A is needed for blocklet B to work properly, then blocklet A is a required dependency for blocklet B. This means that
blocklet A has to be installed alongside blocklet B
blocklet A has to be started before blocklet B
blocklet A can't be deleted if blocklet B is still around.
We've got a bunch of these dependency relationships already set up in our existing blocklets. For example,
Discuss Kit needs Media Kit
Pages Kit needs Media Kit
Blocklet Store needs Meilisearch
If you're wondering why you can't delete a certain blocklet, just click on the highlighted icon in the screenshot to see who's depending on it. Hope that clears things up for you!
1 reply
Hey there! Just wanted to clarify that what you're experiencing is actually a feature, not a bug, of the Blocklet Platform. Composability is super important to us, so when you're putting blocklets together, there are dependency relationships between them. Basically, if blocklet A is needed for blocklet B to work properly, then blocklet A is a required dependency for blocklet B. This means that
We've got a bunch of these dependency relationships already set up in our existing blocklets. For example,
If you're wondering why you can't delete a certain blocklet, just click on the highlighted icon in the screenshot to see who's depending on it. Hope that clears things up for you!