Avoid re-rendering already loaded grid for Product Options (SwiftOtter's SOP-348)

[lbajsarowicz]

Description (*)

In the Product Edit Page, when you open the “Customizable Options” bar, all the Product Options are visible. Suddenly, the loader icon pops up and all the options are rendered again.

The bug was introduced in 2022, and is affecting Product Edit page especiall with a big subsets of options.

Related Pull Requests

Fixed Issues (if relevant)

1. Fixes magento/magento2#<issue_number>

Manual testing scenarios (*)

1. When I open “Customizable Options” section on Edit Product page, and the values of the options are rendered, the loader doesn’t appear afterwards, and the content is not re-rendered.
2. ...

Questions or comments

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

Resolved issues:

1. resolves [Issue] Avoid re-rendering already loaded grid for Product Options (SwiftOtter's SOP-348) #38741: Avoid re-rendering already loaded grid for Product Options (SwiftOtter's SOP-348)

[m2-assistant]

Hi @lbajsarowicz. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.

Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ 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.

[lbajsarowicz]

@magento run all tests

[engcom-Hotel]

@magento create issue

[engcom-Hotel]

Hello @lbajsarowicz,

According to this comment #38741 (comment), we are unable to reproduce the original issue and you will going to provide us some more details on issue reproduction #38741 (comment).

We are still waiting for your reply on the same so that we can move further with this PR. Meanwhile, we are moving this PR to the On Hold bucket.

Let us know whenever you are ready with this.

Thanks