React: Custom react tool gets deleted when subsequent block gets deleted.

[natterstefan]

Current Situation

In my React app, I've created several custom tools that render react components. Everything works fine so far, including interactions with react, content editing (with custom edit views/states in the react component), etc.

@editorjs/editorjs: 2.17.0 is installed.

But the following does not work.

Current Problem(s)

Backspace at position 0 in subsequent block

When hitting backspace, the custom block gets deleted.

(see also https://d.pr/i/DuYgCC/1zprl6UkZb)

Deleting the last item of a list deletes the custom block

(see also https://d.pr/i/LhIjdF/lpEsyTkUPi)

Expected Behaviour

Instead of deleting the custom blocks, they should persist.*

Edit: persist means they should not be deleted, just because the subsequent block gets deleted. The custom block can be deleted (eg. with the tool settings) still.

NOTE: the custom blocks are not contenteditable! This would lead to unwanted side-effects (eg. user can edit react content etc.).

Example App

• https://codesandbox.io/s/editorjs-react-editor-js-example-with-custom-react-component-template-8md15

Related Issues

• Backspace Deleting Whole Block #810 maybe?

---

As always, thank you very much for your help!

[neSpecc]

For now, any block can be deleted. Because all of them are a part of the editable document. We were thinking about a new API feature like Persistent Blocks. I think it will cover your case.

Deleting the last item of a list deletes the custom block

This is strange, need to be researched.

[natterstefan]

Hi @neSpecc,

wow, thanks for the quick response.

For now, any block can be deleted.

That's good and expected, but what is not expected is that the custom block is deleted as shown in the first gif. Why is it deleted when I'm at position 0 (in the subsequent block) and hit the backslash?

I added an update to the description above, because

"Instead of deleting the custom blocks, they should persist.

Was not clear enough. The block can be deleted, but should not automatically (this seems to be the bug) when the subsequent block is deleted.

Still good to know a persistent API is on the table.

This is strange, need to be researched.

Thanks. 👍