fix: custom blocks may error when it is re-created

[teyc]

The custom block wrapper attempts to read the block id of the inner block using getPos(), but the inner block has not been initialized by tiptap yet. Do not attempt to render this block until it is ready

[vercel]

@teyc is attempting to deploy a commit to the TypeCell Team on Vercel.

A member of the Team first needs to authorize it.

[matthewlipski]

Hey, do you have a code snippet or sandbox where the error gets thrown? Can't seem to reproduce it on my end

[teyc]

Thanks for having a look: sample here: https://github.com/teyc/custom-blocknote-bug

[matthewlipski]

Alright I've found the root cause of the issue, so should be able to fix it without needing a workaround. Basically, the editor's content is set before the underlying TipTap editor is done initializing, so any custom blocks which use the BlockNote editor's functions will fail to render. Should be able to fix it by just waiting for the TipTap editor before setting the initial content, just varifying with @YousefED👍

[matthewlipski]

Gonna close this PR and merge #348 since it fixes the root issue and works for both vanilla and React custom blocks, but thanks for bringing this bug to light and helping with this!