6.4 Dev Note Tracking Issue

[properlypurple]

Tracking all Dev Notes from Gutenberg plugin releases 16.2 - 16.7

Please read the information below carefully. If you have questions, ask in #core-editor on Slack or comment here.

Not all developer-related information needs to be in a separate DevNote on the Make Core blog for the field guide. We can group related information. We can already make decisions on some features if it warrants a stand-alone blog post or if the information will be part of a group post.

Stand-alone post

To streamline the process and eliminate bottlenecks, all writers of stand-alone dev notes will write the dev notes on the Make Core Blog. If you need access to write on the Blog, connect with @hellofromtonya or @abhansnuk via Slack or comment here.

Instructions

Details

• Create your note in a new post, - Save as Draft - Enable public preview - Share the link to the public preview in a comment below, as "ready for review" - "For dev notes, each one must have at least two reviewers" (Handbook)

Part of a group post

If the information related to your PR will be part of a group post, please write the dev note in a comment on the PR, so it can be reviewed and, if necessary commented on, by the release docs team or a reviewer.

Before you start writing 📣 please read the handbook pages:

Details

• ⭐️ Writing developer notes
• ⭐️ Style & Substance section of the Post & Comment Guidelines for Make Blog
• ⭐️ Documentation Style Guide - Good for reference, when in doubt, especially when English is not your native language.

The list is incomplete. We are in the process of reviewing plugin release changelogs and add them as we progress on the task.

There are two labels:
needs dev note and has dev note

If you worked on a feature/module/component that definitely needs a dev note, please assign the label needs dev note If you already added the Dev Note to the make blog on draft or as a comment on the PR, please label it has dev note

---

Standalone dev notes:

Block hooks

• Experiment: Auto-inserting blocks on the frontend and in the editor (via REST API) #51449 @ockham
• Block API: Stabilize Block Hooks feature #54293 @gziolo

Miscellaneous dev notes: (these are the ones which already have the neds-dev-note tag, grouped by release)

• RichText: replace deprecated multiline prop with simple multiple instances #54310 @ellatrix

• Theme Previews: Make the back button customizable #54242 @scruffian

• Add edits data to the useEntityRecord #54167 @matiasbenedetto

• Indicate nested paths on __experimentalSaveSpecifiedEntityEdits #54161 @matiasbenedetto

---

• Always render the fallback Popover anchor within the Popover's parent element #53982 @ciampo

---

• Fonts Library: Backend #52704 @matiasbenedetto
• Make useBlockEditingMode() public #52094 @ramonjd

---

• Add new registerInserterMediaCategory API to make media categories extensible #51542 @ntsekouras

[ellatrix]

• RichText: replace deprecated multiline prop with simple multiple instances #54310

Doesn't make sense as a standalone dev note, would be good to add to miscellaneous.

RichText's multiline prop has been deprecated since 6.1 and was scheduled for removal in 6.3. We're leaving the deprecated prop in place, but its functionality has been simplified internally, so you may experience changes. Instead of one large rich text field, each line is now its own rich text field. We added splitting and merging functionality so the fallback is gracious, but some things like paste may work differently. It's worth noting that this prop remains deprecated and all block authors are encourage to use InnerBlocks instead.

[gziolo]

• Block API: Stabilize Block Hooks feature #54293
• Experiment: Auto-inserting blocks on the frontend and in the editor (via REST API) #51449

It's a single feature now called Block Hooks, and @ndiego is helping with the dev note.

[abhansnuk]

Thanks for the efforts that have gone into this and the ongoing review of tickets. In the docs release team and with the cohort, we have been helping newer contributors get involved and had been working through a similar ticket review. Thanks to @bph for sharing that this ticket review is also being done in core-editor, so to avoid duplicating with two lists, we will lose the one we had been working on, and focus effort on this tracker.

Just a signpost to the handbook information, please do not make any dev notes live until seen by the docs release co-leads so that we can keep an overview of where we are and to avoid too many dev notes being published together which can be difficult for those receiving the RSS feed. We also want to build on the efforts from 6.0 onwards to make sure dev notes have useful excerpts and intro paragraphs for search results to help users/ devs know if a note is what they are looking for.

Thanks again to everyone contributing to this. I am @abhanonstopnewsuk on Slack if you need dev note access.

[ntsekouras]

Draft dev note in make core for Add new registerInserterMediaCategory API to make media categories extensible PR is here.

[abhansnuk]

Thanks Nik. I will have a look.

…

________________________________ From: Nik Tsekouras ***@***.***> Sent: 04 October 2023 08:25 To: WordPress/gutenberg ***@***.***> Cc: Abhanonstopnewsuk ***@***.***>; Mention ***@***.***> Subject: Re: [WordPress/gutenberg] 6.4 Dev Note Tracking Issue (Issue #54998) Draft dev note in make core for Add new registerInserterMediaCategory API to make media categories extensible PR<#51542> is here<https://make.wordpress.org/core/?p=108427&preview=1&_ppp=88ba8ff4e5>. — Reply to this email directly, view it on GitHub<#54998 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AH6IIEDAXFF42MV2E34RPELX5UMPXAVCNFSM6AAAAAA5QS3PA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBWGM4DEMRSGQ>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[properlypurple]

If you've been pinged in here, please take a look at the PRs below, and comment if the PR needs a dev note.

• Remove block tools back compat component schedule for deprecated in 6.3 #53115 @getdave
• Export store for the core/customize-widgets package. #52189 @ryanwelcher
• Export the store for the core/edit-widgets pacakage #52190 @ryanwelcher
• Bump plugin minimum supported PHP version to 7.0 #52982 @hellofromtonya
• TabPanel: implement Ariakit internally #52133 @chad1008
• [create-block] Refinements to the create-block-interactive-template package. #52801 @ryanwelcher
• Components: Introduce a basic ProgressBar component #53030 @tyxla
• Font Library: Font Collections frontend #54566 @matiasbenedetto
• Stabilize defaultBlock, directInsert API's and getDirectInsertBlock selector #52083 @sethrubenstein
• Block Editor: Add support for arrays to setImmutably util #52280 @tyxla
• Add runtime support for the wp-style directive #52645 @luisherranz
• Add filter to turn off Interactivity API for a block #52579 @westonruter
• Add support for registering commands without icons #53647 @richtabor
• Allow passing optional afterLoad callbacks to store calls #53363 @DAreRodz
• Warning: Introduce SCRIPT_DEBUG to make the package compatible with webpack 5 #50122 @gziolo
• Interactivity API: router with region-based client-side navigation #53733 @luisherranz
• Interactivity API: add Slot and Fill directives #53958 @DAreRodz
• Make useBlockEditingMode() public #52094 @noisysocks
• Fluid typography: add min and max viewport width configurable options #53081 @ramonjd
• Allow layout controls to be disabled per block from theme.json #53378 @tellthemachines
• Modal: add headerActions prop to render buttons in the header #53328 @ciampo

[abhansnuk]

I am creating Dev Note tracking issues for the items listed above. I will add them to this list. This allows to have an overview of all the Dev Notes in one place.

Standalone dev notes
UPDATE ON BELOW combined these two to be one on the documentation tracker given the note above from @gziolo that these have been combined to be 'Block Hooks'.
WordPress/Documentation-Issue-Tracker#1144

• Dev Note tracking: Experiment: Auto-inserting blocks on the frontend and in the editor (via REST API) Experiment: Auto-inserting blocks on the frontend and in the editor (via REST API) #51449
• Experiment: Auto-inserting blocks on the frontend and in the editor (via REST API) Experiment: Auto-inserting blocks on the frontend and in the editor (via REST API) #51449

Please can you update this with items relating to the Dev Note. If a google doc has not already been started for this, please let me know and I will create it in the docs area we are using for 6.4 and share it with you.

If you have already started the Dev Note in the CMS, please add the public preview link to the ticket.

Miscellaneous Editor Dev Notes for 6.4
This has been set up reading for those writing dev notes in the Make/Core CMS. Please can you add any links and updates to the Docs tracking issue 1146

Thanks so much.

[luisherranz]

The Interactivity API is still private in WP 6.4 and only used internally for Core blocks, so there's nothing to inform yet. I've checked all the related items:

• Add runtime support for the wp-style directive #52645
• Add filter to turn off Interactivity API for a block #52579
• Allow passing optional afterLoad callbacks to store calls #53363
• Interactivity API: router with region-based client-side navigation #53733
• Interactivity API: add Slot and Fill directives #53958