Skip to content
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

magento/magento2#7720 #26470

Merged
merged 11 commits into from
Sep 18, 2020
Merged

Conversation

engcom-Charlie
Copy link
Contributor

Description (*)

Product repository now uses store_id if it is set.

Fixed Issues (if relevant)

  1. Product Repository saves attribute values for existing product always on "Default Store Level" #7720: Product Repository saves attribute values for existing product always on "Default Store Level"

Manual testing scenarios

  1. Create a Product, save it via ProductRepository::save.
  2. Load the Product via ProductRepository::get, pass 0 as storeId parameter.
  3. Save the Product via ProductRepository::save once more.
  4. Make sure catalog_product_entity_* tables contain only records with store_id=0.

Questions or comments

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)

@m2-assistant
Copy link

m2-assistant bot commented Jan 21, 2020

Hi @engcom-Charlie. 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

For more details, please, review the Magento Contributor Guide documentation.

Copy link
Member

@Nazar65 Nazar65 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @engcom-Charlie , please see my review comments, also fix the static tests

Copy link
Contributor

@lbajsarowicz lbajsarowicz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some minor changes to cover the change.

@ghost ghost assigned lbajsarowicz Jan 25, 2020
vadim and others added 2 commits January 27, 2020 11:34
# Conflicts:
#	dev/tests/integration/testsuite/Magento/Catalog/Model/ProductRepositoryTest.php
@magento-engcom-team
Copy link
Contributor

Hi @lbajsarowicz, thank you for the review.
ENGCOM-6698 has been created to process this Pull Request
✳️ @lbajsarowicz, could you please add one of the following labels to the Pull Request?

Label Description
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests

@engcom-Hotel engcom-Hotel self-assigned this Jan 28, 2020
@engcom-Hotel engcom-Hotel added the Auto-Tests: Covered All changes in Pull Request is covered by auto-tests label Jan 28, 2020
@engcom-Hotel
Copy link
Contributor

✔️ QA Passed

@ghost ghost added the Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. label Jun 17, 2020
@sidolov
Copy link
Contributor

sidolov commented Aug 19, 2020

@engcom-Charlie could you please resolve merge conflicts?

# Conflicts:
#	app/code/Magento/Catalog/Test/Unit/Model/ProductRepositoryTest.php
#	dev/tests/integration/testsuite/Magento/Catalog/Model/ProductRepositoryTest.php
@engcom-Charlie
Copy link
Contributor Author

@magento run all tests

@engcom-Charlie
Copy link
Contributor Author

Hi @sidolov, I've done it.

@ghost ghost moved this from Review in Progress to Ready for Testing in Pull Requests Dashboard Aug 20, 2020
@ghost ghost assigned sidolov Aug 20, 2020
@magento-engcom-team
Copy link
Contributor

Hi @sidolov, thank you for the review.
ENGCOM-6698 has been created to process this Pull Request

@engcom-Alfa engcom-Alfa moved this from Ready for Testing to Testing in Progress in Pull Requests Dashboard Sep 4, 2020
@engcom-Alfa
Copy link
Contributor

✔️ QA Passed

Manual testing scenario:

  1. Create a Product, save it via ProductRepository:save ("Simple" for ex.);
  2. Load the Product via ProductRepository::get, pass 0 as storeId parameter;
  3. Save the Product via ProductRepository::save once more. (update Product name for ex.: "Simple (Updated)");
  4. Make sure catalog_product_entity_* tables contain only records with store_id=0.

Before: ✖️ Table catalog_product_entity_int contain records with store_id=0 and store_id=1

2020-09-16_19-32

✖️ and product name updated for Default Store View (store_id=1)

2020-09-16_19-33

After: ✔️ catalog_product_entity_int table contain only records with store_id=0

2020-09-16_19-23
✔️ and product name updated for All Store Views (store_id=0)

2020-09-16_19-26

@engcom-Alfa engcom-Alfa added the QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope label Sep 17, 2020
@engcom-Alfa engcom-Alfa moved this from Testing in Progress to Extended Testing (optional) in Pull Requests Dashboard Sep 17, 2020
@engcom-Echo engcom-Echo moved this from Extended Testing (optional) to Merge in Progress in Pull Requests Dashboard Sep 17, 2020
magento-engcom-team pushed a commit that referenced this pull request Sep 18, 2020
@magento-engcom-team magento-engcom-team merged commit c594093 into magento:2.4-develop Sep 18, 2020
@m2-assistant
Copy link

m2-assistant bot commented Sep 18, 2020

Hi @engcom-Charlie, 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.

@ghost ghost moved this from Merge in Progress to Recently Merged in Pull Requests Dashboard Sep 18, 2020
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 Component: Catalog Priority: P2 A defect with this priority could have functionality issues which are not to expectations. 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
Pull Requests Dashboard
  
Recently Merged
Development

Successfully merging this pull request may close these issues.

None yet

9 participants