Add rich-text source support for WordPress 6.5 #58
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.
Description
See @leoloso's original PR in #57 (extended here) and the related Gutenberg PR: WordPress/gutenberg#43204.
The majority of
html
source type blocks have been converted to userich-text
. The main difference betweenhtml
andrich-text
seems to be thathtml
supports multiline selectors, andrich-text
has a different__unstablePreserveWhiteSpace
supported setting.The
rich-text
-specific__unstablePreserveWhiteSpace
attribute is not currently implemented in the parser for a couple of reasons:__unstable
, which we don't currently use in any other parsing. If this attribute is standardized without the__unstable
prefix, we should support this option.<code>
,<pre>
and verse) to preserve copied newlines at present.Steps to Test
This PR adds tests for
rich-text
attribute sources. Tests can be run viawp-env
andcomposer
: