-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Fix caching Magento Metadata getVersion #26001
Conversation
Hi @luklewluk. Thank you for your contribution
For more details, please, review the Magento Contributor Guide documentation. |
Hi @luklewluk, thanks for your contribution! Please sign the Adobe CLA so we can process this PR. |
Hi @luklewluk, thank you for your contribution! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @luklewluk,
Thank you for contribution! As for me - your changes looks good.
As as part of #24030 changes weren't covered with unit tests - we got regression very soon. In order to prevent such situation in future - could you cover these changes with unit test?
Also please review failing tests and adjust your code / tests to make them pass.
Hi @ihor-sviziev |
lib/internal/Magento/Framework/App/Test/Unit/ProductMetadataTest.php
Outdated
Show resolved
Hide resolved
Hi @ihor-sviziev, thank you for the review. |
@luklewluk thank you for contributing. Please accept Community Contributors team invitation here to gain extended permissions for this repository. |
✔️ QA Passed |
Hi @luklewluk, thank you for your contribution! |
For the record, turning this PR into a patch and applying it to 2.3.3 resolved this issue for me. More details here. |
Fix caching result in ProductMetadata::getVersion.
Description (*)
My change fixes issue that getVersion result never gets cached.
Original Pull Request: #24030
Caching was broken by this commit: 37f6f6a
In order to fix the issue, we should put that line where it was originally.
Fixed Issues (if relevant)
Manual testing scenarios (*)
Questions or comments
Contribution checklist (*)