Fix: properly merged schema during mergeSchemas part in getBlockContentSchemaFromTransforms

[USERSATOSHI]

What?

Closes #70612

This PR fixes the bug where merging schemas causes top level classes property to convert from array to object with indices as keys.

Why?

As the classes gets converted to Object the cleanNodeList function fails when it tries to map the classes property.
Error at this line

How?

The Solution checks whether b[key] is an array or not, if it is an array , set a[key] to be copy of b[key] else the original object shallow clone.

Testing Instructions

Follow the instructions of #70612

Screenshots or screencast

Before

Screen.Recording.2025-07-04.at.2.08.59.PM.mov

Results

Screen.Recording.2025-07-04.at.2.35.36.PM.mov

Block Transform Code

Screen.Recording.2025-07-04.at.2.37.14.PM.mov

[github-actions]

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: USERSATOSHI <[email protected]>
Co-authored-by: desrosj <[email protected]>
Co-authored-by: getdave <[email protected]>

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

[USERSATOSHI]

oh god, I messed up while trying to merge trunk, sorry.

[USERSATOSHI]

Hi, Sorry to all the reviewers that got the notifications from this PR. I was trying to merge the trunk to update the branch to latest commit but accidentally rebased it.

I have fixed the branch but sorry for the ping that got requested due to this mishap.
I will try to be more mindly-aware of what I am doing from next time.

Sorry again for all this.
Regards

[desrosj]

@USERSATOSHI Don't worry about it! We've all been there! 😅 It happens occasionally and is not a big deal.

[USERSATOSHI]

😅

[getdave]

@USERSATOSHI Thanks for the PR. Would it be possible for you to write some tests to replicate the bug you were experiencing and show that your changes resolve this issue 🙏

[USERSATOSHI]

Thanks for the PR. Would it be possible for you to write some tests to replicate the bug you were experiencing and show that your changes resolve this issue 🙏

Hi @getdave, Just to confirm, I need to write an unit test which would validate the working of the patch, or

a reproduction report and a patch testing report showing the bug replication and patch testing?

If it is the latter , for bug replicate there is a failing action of this
https://github.com/WordPress/gutenberg/actions/runs/16409380285/job/46361037826?pr=70635#step:6:1045

Which should validate that bug replication.

And for patch testing report , I can write the report. 😄

[getdave]

I was thinking of adding some coverage to the existing unit tests in packages/blocks/src/api/raw-handling/test/utils.js.

[USERSATOSHI]

I was thinking of adding some coverage to the existing unit tests in packages/blocks/src/api/raw-handling/test/utils.js.

oh got it, I will add the tests for this then. thank you

[USERSATOSHI]

Hi @getdave, I added tests for coverage of this issue.

Before	After

[Adi-ty]

LGTM🚀

The Patch fixes the issue I am no longer getting the error.

Bug Reproduction link for anyone to check: #70612 (comment)

Before

After