Compatible with Magento 2.4.7, as backward compatibility has been lost in the Magento\Catalog\Model\ProductRepository class #318
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As of Magento 2.4.7, backward compatibility has been lost in the Magento\Catalog\Model\ProductRepository class. This pull request aims to fix this issue.
Check the issue page in the Magento repo for reference: magento/magento2#38669.
The changes made in this pull request are as follows:
__construct()
method with multiple methods that utilize ObjectManager to instantiate the necessary instances. This change was made to prevent errors during code complication:$stockRegistry
.$excludedCustomAttributes
property with a constant. Using a class constant for a fixed value that will be used within a method helps to clearly define and identify the value as a constant for that class. It also ensures that the value remains consistent and cannot be changed or modified within the class methods.$attributes
param, as it must be of type array since it is used as the second param in anarray_merge()
function, which requires an array type.