Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Type-related labels to choose from: [Type] Automated Testing, [Type] Breaking Change, [Type] Bug, [Type] Build Tooling, [Type] Code Quality, [Type] Copy, [Type] Developer Documentation, [Type] Enhancement, [Type] Experimental, [Type] Feature, [Type] New API, [Type] Task, [Type] Technical Prototype, [Type] Performance, [Type] Project Management, [Type] Regression, [Type] Security, [Type] WP Core Ticket, Backport from WordPress Core, Gutenberg Plugin.
• Labels found: .

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: shimotmk <shimotomoki@git.wordpress.org>
Co-authored-by: t-hamano <wildworks@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Thank you for your review.

If press the rest button for Resolution only (not Reset all), should sizeSlug be set to undefined ?

If select full in SelectControl, should sizeSlug be set to undefined ?

Set it to undefined when it matches DEFAULT_MEDIA_SIZE_SLUG.
I thought more consistent with the other attributes.

<!-- wp:post-featured-image {"sizeSlug":"full"} /-->
<!-- wp:post-featured-image /-->

After some research, I found that these two HTMLs can have different results. See #70526 for more details.

Set it to undefined when it matches DEFAULT_MEDIA_SIZE_SLUG.

In other words, this approach means that users will no longer be able to explicitly select the full media size, and the post-thumbnail media size will be used on the frontend.

This may affect some themes, so we might want to explicitly apply DEFAULT_MEDIA_SIZE_SLUG instead of undefined in the resetAll. So, in my opinion, your first commit is the right approach after all 😄

Let me know what you think!

Thanks for looking into this!

Default and full are different.

I considered setting a sizeSlug default in block.json, but it seems best to avoid that for compatibility reasons.

Appearance also has a default option, so I think it's a good idea to add a default.

Added defaults to options so that they can be reset to their initial values.😄

@shimotmk Perhaps I was not clear enough. I am not proposing to add a default option in this PR. Whether to add a default option needs to be discussed carefully in #70526.

What I suggest is to simply apply this commit to the trunk.

Sorry for bothering you.
I reverted to the first commit and merged the latest trunk.

After some research, I found a similar discussion about the UI of the default options for the aspect ratio of the cover block.
#60224 (comment)