[FIX] Support Rich-Text block source #203
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pristas-peter
approved these changes
Mar 22, 2024
|
Hi all! Any reason this PR is still unmerged? |
This was referenced Jul 19, 2024
|
Fixed for me, a shame that the plugin seems unmaintained. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In anticipation of the forthcoming launch of WordPress 6.5, a significant transition has been made from HTML sources to rich-text formats.
Given the absence of support for the rich-text source in
wp-graphql-gutenberg, the present Pull Request has been introduced to incorporate this capability.