Experimental: Remove children matcher in favor of HTML #1907
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related: #421, #466
The
children
matcher was introduced in #466 as a solution to the issue where serializing content as a React element in thesave
implementation would require the block implementer to usedangerouslySetInnerHTML
, which was unnatural (and scare-inducing) compared to typical React children rendering. The result ofsave
is only ever used to generate the string content to be saved in post content, so escaping the rich HTML of an Editable field value is undesirable.This pull request seeks to explore an alternative solution, preferring to manage the Editable (TinyMCE) value as a string, and overcoming the issue of
dangerouslySetInnerHTML
by intercepting and traversing the return value ofsave
to replace a stringchildren
prop with the equivalentdangerouslySetInnerHTML
. The magic occurs inserializer.js
:See also: https://github.com/elierotenberg/react-traverse
This has a few benefits:
nodeListToReact
/renderToString
dance in Editable (more performant)isEqual
on element trees)concatChildren
because concatenating values is a simple addition operator with stringsThis is a work-in-progress, notably:
dangerouslySetInnerHTML
in theTinyMCE
component and instead set content via traditional TinyMCEsetContent
(with sanitization)