fix items getChilderen returns empty array for parent cart items when…

[Gerke-W]

Description (*)

This pull request addresses a known issue in Magento Checkout where child products are not displayed correctly when the cart contains more than 20 products and pagination is enabled. the issue is that $_item->getHasChildren() returns NULL and $_item->getChilderen() returns NULL for configurable products when the cart is paginated.

To fix this, I've implemented the following changes:

1. Added updateCollectionWithQuoteItems Method: This method iterates over the items in the collection and updates them with the corresponding quote items. It ensures that the correct items are displayed in the cart, even when pagination is active.

These changes ensure that $_item->getHasChildren() returns true for configurable products, and $_item->getChildren() returns the correct array of child items, regardless of pagination status. This resolves the issue described in #34507 and improves the reliability of the checkout process.

Fixed Issues (if relevant)

1. Fixes $_item->getChildren() returns empty array for parent cart items when cart is paginated #34507

Related Pull Requests

35739

Manual testing scenarios (*)

1. Add both configurable and non-configurable products to the cart.
2. Print the $_item->getHasChildren() property in the Magento_Checkout/cart/item/default.phtml template.
3. Observe the function output with and without pagination in the cart.

Expected result

The cart should behave as expected even when underlying code is calling for childeren of a products i.e. $_item->getHasChildren() and $_item->getChilderen().

[m2-assistant]

Hi @Gerke-W. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.
❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

---

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

[Gerke-W]

@magento run all tests