[wp-trac] [WordPress Trac] #60525: Block Bindings:

WordPress Trac noreply at wordpress.org
Tue Feb 13 14:39:37 UTC 2024


#60525: Block Bindings:
--------------------------+---------------------
 Reporter:  gziolo        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.5
Component:  Editor        |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+---------------------
Description changed by gziolo:

Old description:

> While testing Block Bindings API, we realized that we don't have a robust
> mechanism for extending block context of supported block types. The
> approach to manually update every block type's `usesContext` in
> `block.json` file doesn’t scale at all. Hardocing the list of injected
> `useContext` entries is also limiting. We decided to formalize it in the
> registration of the block bindings source. This way, every author of the
> block bindings source can decide what entries from the block context they
> want to consume.

New description:

 While testing Block Bindings API, we realized that we don't have a robust
 mechanism for extending block context of supported block types. The
 approach to manually update every block type's `usesContext` in
 `block.json` file doesn’t scale at all. Hardocing the list of injected
 `useContext` entries is also limiting. We decided to formalize it in the
 registration of the block bindings source. This way, every author of the
 block bindings source can decide what entries from the block context they
 want to consume.

 Related changes proposed are also in the Gutenberg plugin:
 https://github.com/WordPress/gutenberg/pull/58554.

--

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/60525#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list