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

Removed client preference from Magento\ReleaseNotification module #22179

Closed

Conversation

tephereth
Copy link

Description (*)

A preference for ClientInterface was wrongly present in Magento\ReleaseNotification module. This fix is related to the MSI issue: magento/inventory#2128 and to the MSI pull request: magento/inventory#2144

Fixed Issues (if relevant)

Related to MSI issue: magento/inventory#2128

Manual testing scenarios (*)

Testable on MSI, see magento/inventory#2144

Contribution checklist (*)

  • [x ] Pull request has a meaningful description of its purpose
  • [ x] 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 on Travis CI are green)

@m2-assistant
Copy link

m2-assistant bot commented Apr 5, 2019

Hi @tephereth. 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-engcom-team give me test instance - deploy test instance based on PR changes
  • @magento-engcom-team give me 2.3-develop instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Assistant documentation

@orlangur orlangur self-assigned this Apr 6, 2019
Copy link
Contributor

@orlangur orlangur left a comment

Choose a reason for hiding this comment

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

@tephereth
Copy link
Author

Working on this fix for MSI I've noticed that the ClientInterface preference involves many classes of InventoryDistanceBasedSourceSelection; first thought was to add type direct in the di.xml of the MSI module and ReleaseNotification module. But since most of Magento\Framework preferences are anyway stored in the general etc/di.xml, I guess the solution that @orlangur suggested is cleaner.

Copy link
Contributor

@orlangur orlangur left a comment

Choose a reason for hiding this comment

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

Please squash changes into a single commit so that we have perfectly clean history 😉

@tephereth tephereth force-pushed the remove-client-preference branch from 3561c5a to 5b9ed54 Compare April 6, 2019 12:48
@tephereth
Copy link
Author

@orlangur, commits squashed

@tephereth tephereth requested a review from orlangur April 6, 2019 12:49
@orlangur
Copy link
Contributor

orlangur commented Apr 6, 2019

Thanks @tephereth! Would be nice to grep for preference.*framework in app/code to catch all such also.

@magento-engcom-team magento-engcom-team added the partners-contribution Pull Request is created by Magento Partner label Apr 6, 2019
@magento-engcom-team
Copy link
Contributor

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

@orlangur
Copy link
Contributor

orlangur commented Apr 8, 2019

This actually duplicates #21540

@orlangur orlangur closed this Apr 8, 2019
@m2-assistant
Copy link

m2-assistant bot commented Apr 8, 2019

Hi @tephereth, 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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants