Skip to content

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

Conversation

kodubovik
Copy link
Contributor

@kodubovik kodubovik commented Jun 19, 2020

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 (*)

  • 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)
  • All automated tests passed successfully (all builds are green)

Resolved issues:

  1. resolves [Issue] Fix shipping address id getter misspelling #28982: Fix shipping address id getter misspelling

@m2-assistant
Copy link

m2-assistant bot commented Jun 19, 2020

Hi @kodubovik. Thank you for your contribution
Here is some useful tips 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

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.

@kodubovik
Copy link
Contributor Author

@magento run all tests

@ihor-sviziev ihor-sviziev self-assigned this Jun 19, 2020
@ihor-sviziev
Copy link
Contributor

ihor-sviziev commented Jun 19, 2020

@kodubovik good catch! This issue was there for 6 years!
I think it could be checked with adding breakpoint with xdebug.

Could you remove phpdoc block for Address class, as static tests complaining about it?

@ihor-sviziev ihor-sviziev added Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Award: bug fix Award: test coverage Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Jun 19, 2020
Copy link
Contributor

@ihor-sviziev ihor-sviziev left a 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?

@kodubovik
Copy link
Contributor Author

@magento run all tests

@magento-engcom-team
Copy link
Contributor

Hi @ihor-sviziev, thank you for the review.
ENGCOM-7723 has been created to process this Pull Request

@magento-engcom-team
Copy link
Contributor

@kodubovik thank you for contributing. Please accept Community Contributors team invitation here to gain extended permissions for this repository.

@engcom-Delta engcom-Delta self-assigned this Jul 2, 2020
@engcom-Delta
Copy link
Contributor

✔️ QA passed
Was checked cases with place order as guest, place order as registered customer with same/different billing and shipping address, checkout with multiple addresses.

@engcom-Kilo engcom-Kilo self-assigned this Jul 2, 2020
@engcom-Kilo engcom-Kilo added the QA: Ready to add to Regression Scope Should be analyzed and added to Regression Testing Scope(if applicable) label Jul 2, 2020
@engcom-Delta
Copy link
Contributor

@magento create issue

@engcom-Delta engcom-Delta added QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope and removed QA: Ready to add to Regression Scope Should be analyzed and added to Regression Testing Scope(if applicable) labels Jul 3, 2020
@slavvka slavvka added the Priority: P3 May be fixed according to the position in the backlog. label Jul 8, 2020
@slavvka slavvka added this to the 2.4.1 milestone Jul 8, 2020
@magento-engcom-team magento-engcom-team merged commit 468cbec into magento:2.4-develop Jul 9, 2020
@m2-assistant
Copy link

m2-assistant bot commented Jul 9, 2020

Hi @kodubovik, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Award: bug fix Award: test coverage Component: Sales Priority: P3 May be fixed according to the position in the backlog. Progress: accept QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4 Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

[Issue] Fix shipping address id getter misspelling
6 participants