Skip to content

Block Processor: add get_attribute_replacement().#11130

Draft
dmsnell wants to merge 1 commit intoWordPress:trunkfrom
dmsnell:blocks/block-processor-attribute-replacement
Draft

Block Processor: add get_attribute_replacement().#11130
dmsnell wants to merge 1 commit intoWordPress:trunkfrom
dmsnell:blocks/block-processor-attribute-replacement

Conversation

@dmsnell
Copy link
Member

@dmsnell dmsnell commented Mar 3, 2026

Status

This is experimental work.

Description

There are useful times to modify the JSON attributes within a block. This change proposes a new method which performs serialization on a set of new attributes, and returns an update description on how to apply those attributes textually against a document to make the edit.

This returns a WP_HTML_Text_Replacement instance with the range of bytes that should be replaced, as well as the serialized content of the update.

There are useful times to modify the JSON attributes within a block.
This change proposes a new method which performs serialization on a
set of new attributes, and returns an update description on how to
apply those attributes textually against a document to make the edit.

This returns a `WP_HTML_Text_Replacement` instance with the range of
bytes that should be replaced, as well as the serialized content of
the update.
@github-actions
Copy link

github-actions bot commented Mar 3, 2026

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant