-
Notifications
You must be signed in to change notification settings - Fork 9.4k
#16832 - Reworked query in getAttributeRawValue so that it returns a store specific value even if there is no default value #23369
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…cific value even if there is no default value
Hi @semajeg. Thank you for your contribution
For more details, please, review the Magento Contributor Assistant documentation |
app/code/Magento/Catalog/Model/ResourceModel/AbstractResource.php
Outdated
Show resolved
Hide resolved
…om failing" This reverts commit 35c5185.
…f function in getAttributeRawValue
…g\Model\ResourceModel\AbstractResource for static tests
Hey @dmanners, got a weird issue here. The "Database Compare Build" is failing now, but when you look at the details, it says it's all passed. Any thoughts? |
Hi @josefbehr, thank you for the review.
|
✔️ QA passed |
…it returns a store specific value even if there is no default value #23369
Hi @semajeg, thank you for your contribution! |
Description (*)
Reworked query in getAttributeRawValue so that it returns a store specific value even if there is no default value
The query being generated in this function was querying the default value and then joining onto the store value, so if the default value was not present then it would not return a store value, even if there was one.
The query has been changed so that it left joins on both the default value and the store value, so that it does not prevent the return of a store value if there is no default
Fixed Issues (if relevant)
Manual testing scenarios
Questions or comments
Though the tech guidelines say "1.3.1. All new PHP files MUST have strict type mode enabled by starting with declare(strict_types=1);. All updated PHP files SHOULD have strict type mode enabled. PHP interfaces SHOULD NOT have this declaration.". This was discussed at the mm19uk contribution day with Tom Erskine and we decided that this PR should not do that to this file,since it will widen the scope of the PR too much and probably cause a LOT of knock on effects