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

Use the same greeting as in other Magento Customer emails #27589

Merged
merged 1 commit into from
Apr 18, 2020

Conversation

ptylek
Copy link
Contributor

@ptylek ptylek commented Apr 4, 2020

Description (*)

In all Magento_Customer emails, there is proper greeting using customer name instead of Hello.

Related Pull Requests

These changes were moved from #27356 as the other PR is focused on duplicated content, not on changes to greeting.

Fixed Issues (if relevant)

not found

Manual testing scenarios (*)

  1. As a logged in user go to User Area - My Account Information section and change password / email.
  2. Go to your email box and check those emails.

Questions or comments

All emails use
<p class="greeting">{{trans "%name," name=$customer.name}}</p>
Maybe we can switch it to
<p class="greeting">{{var customer.name}},</p>
?

That would wider the scope of this PR in order to check all emails.

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 Apr 4, 2020

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

@lbajsarowicz
Copy link
Contributor

@ptylek As I promised, please find my Test coverage for your PR: #27606

lbajsarowicz added a commit to lbajsarowicz/magento2-contributions that referenced this pull request Apr 5, 2020
lbajsarowicz added a commit to lbajsarowicz/magento2-contributions that referenced this pull request Apr 5, 2020
@rogyar rogyar self-assigned this Apr 6, 2020
@rogyar
Copy link
Contributor

rogyar commented Apr 6, 2020

Hi @lbajsarowicz. How would you like to proceed with this one? Should @ptylek copy the tests over to this PR and close yours? Trying to figure out the best way to process both PRs.

Thank you.

@lbajsarowicz
Copy link
Contributor

If you merge mine, his would be also tagged as merged.

magento-engcom-team added a commit that referenced this pull request Apr 18, 2020
 - Merge Pull Request #27606 from lbajsarowicz/magento2:test-coverage/27589-email-integration-tests
 - Merged commits:
   1. 1ac923d
   2. 16cb18d
   3. f882122
   4. 82224a6
   5. cd895a5
   6. d4b8083
magento-engcom-team added a commit that referenced this pull request Apr 18, 2020
…op expedited

Accepted Community Pull Requests:
 - #26293: Bugfix - Customer emails are not being sent from admin if customer is from store "0" (by @matheusgontijo)
 - #27606: Test coverage for PR #27589 (E-mail templates) (by @lbajsarowicz)
 - #27841: [MFTF] Remove redundant Index and Flush Cache action group (by @Usik2203)
 - #27692: [MFTF] Use ActionGroup for checking category save success message. (by @Usik2203)
 - #27843: [MFTF] Added assertion to AssertAdminSuccessLoginActionGroup (by @Usik2203)
@magento-engcom-team magento-engcom-team merged commit 1ac923d into magento:2.4-develop Apr 18, 2020
@m2-assistant
Copy link

m2-assistant bot commented Apr 18, 2020

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

4 participants