Block Editor: Avoid default block insertion if no default block type #15786
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.
Previously: #15543 (comment)
Cherry-picks 2f1a82f from #15543 (temporarily)
This pull request seeks to resolve an error which occurs when deleting the last of the blocks in a post, if there is no default block type.
Implementation Notes:
getDefaultBlockName
is implemented to handle unregistrations, and thus we should be consistent to respect this nullable return type.gutenberg/packages/blocks/src/store/selectors.js
Line 76 in d15c484
gutenberg/packages/blocks/src/store/reducer.js
Lines 110 to 114 in d15c484
Testing Instructions:
Verify no error when deleting all blocks if the default block type is disabled:
wp.data.dispatch( 'core/blocks' ).removeBlockTypes( wp.data.select( 'core/blocks' ).getDefaultBlockName() );