Command Palette: Block commands that do not work on the selected block are displayed

[t-hamano]

Description

Related to #52509

By #52509, commands related to blocks were added. However, you will see commands that are not expected to be used with the selected block.

Step-by-step reproduction instructions

N/A

Screenshots, screen recording, code snippet

382ee8aae45d89414776d677731ec185.mp4

Environment info

No response

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Yes

[ntsekouras]

Thanks for the issue. I'll open a PR about the grouping commands soon.

[t-hamano]

Thank you for bringing this issue to your attention. From my new research, it seems that all block commands need to be given some sort of condition.

• Ungroup / Group : Should check if the block is groupable or ungroupable; the useConvertToGroupButtonProps hook may be reusable. [Commands]: Add group/ungroup commands only when eligible #53988
• Move to: Should not be displayed when there is only one block or when the move is locked [Commands]: Fix block editor commands availability #53994
• Add after / Add before: When a default block cannot be inserted, it should not be displayed. For example, this is the case when the paragraph block is excluded by the allowed_block_types_all hook. [Commands]: Fix block editor commands availability #53994
• Remove: Should not be displayed when canRemoveBlocks is false. [Commands]: Fix block editor commands availability #53994
• Duplicate: Should not be displayed when the block cannot be duplicated. [Commands]: Fix block editor commands availability #53994