Has this bug been raised before?
Description
When creating a custom inline void plugin element (e.g., a placeholder like {{First Name}}) and registering it within a block plugin, the element renders correctly in the editor but produces no output when serializing to email or HTML via @yoopta/exports.
The serializer appears to skip or not recognise custom inline void element types that aren't part of the core plugin set (like link or mention). The element data is present in the editor value JSON, but the html.serialize() and email export paths return an empty string for these nodes.
I believe this issue happens because of the serializeTextNodes in the getEmail functions, as it only handles for fixed nodes with the 'text' in them.
Do you want to work on this issue?
Yes
Has this bug been raised before?
Description
When creating a custom inline void plugin element (e.g., a placeholder like
{{First Name}}) and registering it within a block plugin, the element renders correctly in the editor but produces no output when serializing to email or HTML via @yoopta/exports.The serializer appears to skip or not recognise custom inline void element types that aren't part of the core plugin set (like link or mention). The element data is present in the editor value JSON, but the
html.serialize()and email export paths return an empty string for these nodes.I believe this issue happens because of the
serializeTextNodesin thegetEmailfunctions, as it only handles for fixed nodes with the'text'in them.Do you want to work on this issue?
Yes