Docs: Use 'key' in 'editor.BlockEdit' filter code examples #58119
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.
What?
PR updates the
editor.BlockEdit
filter code examples and sets statickey
for the originalBlockEdit
component.Why?
tl;dr - it is just good practice, and most folks don't need to worry about technical details.
The
key
prevents theBlockEdit
component from remounting if its position changes after the initial render. When thekey
is provided, React will use it as a part of the position instead of the order in the parent component.Remounting can have unexpected side effects and sometimes even affect the performance.
Testing Instructions
None