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

'Ship Here' in CamelCase as that's how it is written elsewhere #28547

Conversation

woutk88
Copy link
Contributor

@woutk88 woutk88 commented Jun 5, 2020

Description (*)

In the checkout shipping address modal the text in the primary button was written with a lowercase 'h'. On all other places, and in the translation files, it is written with a capital: 'Ship Here'. As a result, the button with the lowercase version 'Ship here' isn't translated.

Related Pull Requests

Fixed Issues (if relevant)

Manual testing scenarios (*)

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)

Resolved issues:

  1. resolves [Issue] 'Ship Here' in CamelCase as that's how it is written elsewhere #28685: 'Ship Here' in CamelCase as that's how it is written elsewhere

@m2-assistant
Copy link

m2-assistant bot commented Jun 5, 2020

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

@magento-engcom-team magento-engcom-team added Area: Frontend Component: Checkout Release Line: 2.4 Partner: MediaCT Pull Request is created by partner MediaCT partners-contribution Pull Request is created by Magento Partner labels Jun 5, 2020
@rogyar rogyar self-assigned this Jun 7, 2020
@rogyar
Copy link
Contributor

rogyar commented Jun 7, 2020

@magento run Functional Tests CE

@rogyar rogyar added Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests Cleanup labels Jun 8, 2020
@magento-engcom-team
Copy link
Contributor

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

@ghost ghost assigned ptylek Jun 8, 2020
@magento-engcom-team
Copy link
Contributor

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

@engcom-Alfa
Copy link
Contributor

✔️ QA Passed

Preconditions:

  1. Has a simple product;
  2. Logged as Customer to Storefront with at least 1 saved address;

Manual testing scenario:

  1. Add translation for "Ship Here" in translation file; ("Ship Here","Ship Here (translated)" for ex.);
  2. Add product to Cart;
  3. Click on "Proceed to Checkout" button;
  4. Click on "+ New Address" button;

Before: ✖️ The phrase was not translated

screenshot_47

After: ✔️ The phrase was successfully translated

screenshot_48

@engcom-Charlie
Copy link
Contributor

@magento run all tests

@slavvka slavvka added Priority: P3 May be fixed according to the position in the backlog. Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Jun 9, 2020
@slavvka slavvka added this to the 2.4.1 milestone Jun 9, 2020
@magento-engcom-team magento-engcom-team merged commit df2ba0c into magento:2.4-develop Jun 9, 2020
@m2-assistant
Copy link

m2-assistant bot commented Jun 9, 2020

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

@woutk88 woutk88 deleted the feature/fix-ship-here-translation branch June 11, 2020 09:55
@engcom-Alfa
Copy link
Contributor

@magento create issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Frontend Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests Cleanup Component: Checkout Partner: MediaCT Pull Request is created by partner MediaCT partners-contribution Pull Request is created by Magento Partner Priority: P3 May be fixed according to the position in the backlog. Progress: accept 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] 'Ship Here' in CamelCase as that's how it is written elsewhere
7 participants