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

Fix referenced to "store", changing to "scope" in Framework/Mail components #20621

Merged
merged 2 commits into from
Feb 24, 2019
Merged

Fix referenced to "store", changing to "scope" in Framework/Mail components #20621

merged 2 commits into from
Feb 24, 2019

Conversation

gwharton
Copy link
Contributor

Description (*)

Changes introduced in PR#18471 used references to "store" in framework components. This PR changes these references to "scope" instead. The same changes are being proposed to the 2.2-develop branch in PR #18472.

The setFromByStore function is deprecated and a new function setFromByScope is introduced.

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 on Travis CI are green)

@magento-engcom-team
Copy link
Contributor

Hi @gwharton. 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

@magento-engcom-team magento-engcom-team added this to the Release: 2.3.1 milestone Jan 25, 2019
@magento-engcom-team
Copy link
Contributor

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

@okorshenko okorshenko removed this from the Release: 2.3.1 milestone Jan 28, 2019
@sivaschenko
Copy link
Member

Hi @gwharton thank you for the pull request, however, we cannot accept this contribution. We are not accepting new public methods to classes marked as API. I have to close this pull request.

Please feel free to contact me if you have any comments or questions.

@ghost
Copy link

ghost commented Feb 12, 2019

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

@gwharton
Copy link
Contributor Author

gwharton commented Feb 12, 2019

@ihor-sviziev can you let me know the way forward on this. The same changes are also proposed as part of #18472 and were requested by @buskamuza.

If this PR doesn't go through, then it doesn't affect the way magento works, its just a naming thing, but if it also holds up #18472 and we miss the 2.2.8 deadline, then the other changes in #18472 would not get applied and the 2.2 branch would go for another 2-3 months with broken email sender from addresses.

@ihor-sviziev
Copy link
Contributor

Hi @gwharton,
Will contact @buskamuza and will decide what to do

@buskamuza
Copy link
Contributor

The new method (setFromByStore()) has been added in #18471 . This PR only renames it according to a previous discussion. This change does not impact backward compatibility, so it should be possible to merge it.

@sivaschenko sivaschenko reopened this Feb 13, 2019
@sivaschenko
Copy link
Member

Hi @gwharton , sorry for the confusion. Reopening as the backward incompatible change was approved by an architect. This pull request will be soon merged to mainline.

@melnikovi melnikovi self-requested a review February 19, 2019 23:50
@magento-engcom-team magento-engcom-team merged commit bd0c6f3 into magento:2.3-develop Feb 24, 2019
@ghost
Copy link

ghost commented Feb 24, 2019

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

magento-engcom-team pushed a commit that referenced this pull request Feb 24, 2019
@magento-engcom-team magento-engcom-team added this to the Release: 2.3.2 milestone Feb 24, 2019
@gwharton gwharton deleted the 2.3-develop-emailfix branch April 4, 2019 13:25
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.

7 participants