-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Fix shipping address id getter misspelling #28810
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 shipping address id getter misspelling #28810
Conversation
Hi @kodubovik. Thank you for your contribution
❗ Automated tests can be triggered manually with an appropriate comment:
You can find more information about the builds here ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review. For more details, please, review the Magento Contributor Guide documentation. |
@magento run all tests |
@kodubovik good catch! This issue was there for 6 years! Could you remove phpdoc block for |
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.
Could you remove phpdoc block for Address class, as static tests complaining about it?
@magento run all tests |
Hi @ihor-sviziev, thank you for the review. |
@kodubovik thank you for contributing. Please accept Community Contributors team invitation here to gain extended permissions for this repository. |
✔️ QA passed |
@magento create issue |
Hi @kodubovik, thank you for your contribution! |
Description (*)
Fixed a shipping address id getter misspelling in the sales order address save handler. Misspelt getter caused unneeded requests to the database on each order save which might create deadlocks.
Manual testing scenarios (*)
This bug can not be validated manually as there're no effects visible on the front-end.
The fix includes Unit tests to validate that address save handler does not execute save attribute method when it's not needed.
Contribution checklist (*)
Resolved issues: