-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
6.4 Dev Note Tracking Issue #54998
Comments
Doesn't make sense as a standalone dev note, would be good to add to miscellaneous.
|
It's a single feature now called Block Hooks, and @ndiego is helping with the dev note. |
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. |
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: ***@***.***>
|
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
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 Thanks so much. |
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:
|
Font Library was punted to 6.5, and for that reason not included in 6.4, so a dev note is not required. |
@properlypurple Yes, but probably just updating the existing InnerBlocks tutorial doc to include these stabilized apis? When would you need those updates by? |
After a conversation with @abhansnuk last night, we agreed that I will centralize the Dev Notes wrangling here. |
Hi @sethrubenstein Thank you! Tt would help to alert people that something has changed even if it's just a one paragraph, update to the docs would also be quite appreciated. The deadline for the blurb is Monday, so we get it into the FieldGuide on Tuesday. For the docs updated, it should happen between now and and Nov 7 (release date for 6.4) |
I'm not sure whether it requires a dev note. From the WordPress core, it's mostly an internal optimization to send less code to the browser. It could be useful for folks using
However, it's something that we could as well put into the README for |
This was a minor fix to bring a component in line with some others. No dev note needed. |
My contribution to the miscellaneous dev notes: Add edits data to the useEntityRecordNow, the useEntityRecord adds to its output a key called const widget = useEntityRecord( 'root', 'widget', 1 );
widget.edit( { hello: 'foo' } ); Expected result: {
edits: { hello: 'foo' }
...
} Indicate nested paths on __experimentalSaveSpecifiedEntityEditsPreviously, one could only indicate which top-level properties one wanted to save using __experimentalSaveSpecifiedEntityEdits. So we were limited to doing something like this: __experimentalSaveSpecifiedEntityEdits( 'root', 'globalStyles', globalStylesId, [ 'settings' ] ); The latest changes enable developers to indicate which nested paths want to be saved into the database. For example, if one made some client-side changes to the fontFamilies array of the global styles settings ( settings.typography.fontFamilies ) and wants to save to the database only those changes instead of all the changes that the settings objects may have. __experimentalSaveSpecifiedEntityEdits( 'root', 'globalStyles', globalStylesId, [ 'settings.typography.fontFamilies' ] ); Thanks, @bph and @properlypurple for the ping and for running this. |
@youknowriad I'll write the dev note for #53982 |
Site Editor: Make the back to dashboard link text customizableIt has been possible to customize the "Back to Dashboard" link in the Site Editor since 6.2, but not the link text. Now it is possible to also customize the text of the link, by providing a
This gives extenders the ability to ensure that link labels are updated when they change this back button, which is important for accessibility. |
Dev Note for
Developer Experience: Exporting stores for the core/customize-widgets and core/edit-widgets packagesMost code examples import the store directly from the package and it is now possible from these packages as well. |
Dev note here: |
Thanks for the ping @properlypurple! Dev note for disabling layout controls from theme.json is here. |
The state of Gutenberg Dev NotesWe will have four post about developer relevant Gutenberg changes in 6.4 on Make Blog: Two of them are in review
cc: @hector @anne @richtabor @Mamaduka are there things missing? Huge thank you to @properlypurple for surfacing all PRs possibly needing Dev Notes. |
Thank you @bph and @properlypurple , and everyone working on these dev notes. I think Birgit is already doing a first review, so I will add second review comments below.
General comments about this and other dev notes b) Categories |
@bph apologies, it looks like I missed that Block Supports: Add background image support to Group block (#53934) also could use a dev note for 6.4. As with other block supports for previous releases, I think this could be added to your Miscellaneous Editor changes in WordPress 6.4 post, as it's just a short one to make sure folks know how to opt-in for their themes. I've drafted a short dev note to be added to that post over in this comment: #53934 (comment) |
Thank you @andrewserong
That bears the question: Are there plans in place to broaden the support? |
@sethrubenstein @andrewserong both items made it into the Misc Editor changes dev note. |
@abhansnuk I am not aware of the discussions regarding additional annotating source for the link or the Updates category. For 6.1 and 6.2 I didn't implement either |
Suggest we take the question on the link @abhansnuk to accessibility. This can be implemented later if needed. In terms of Updates category, is there a definition or description of what category to use in the handbook? |
Yes! I touched on it earlier in the dev note in the sentence "Ideas for enhancements in future releases are being tracked in this Github issue: #54336", but we could add another similar sentence at the end there to make sure it's clear. How about:
|
Field Guide published: WordPress 6.4 Field Guide |
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
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
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
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
The text was updated successfully, but these errors were encountered: