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

MC-23553: Invalid Template Strings when Translate Inline enabled #32002

Merged
merged 4 commits into from
Mar 3, 2021

Conversation

namlier
Copy link
Contributor

@namlier namlier commented Feb 9, 2021

Bug P2

Description (*)

This is a usability issue.

Fixed Issues (if relevant)

  1. Fixes Invalid Template Strings when Translate Inline enabled #32000

Manual testing scenarios (*)

Preconditions:

  1. Magento installed
  2. Several products and a customer is created
  3. Add product to cart on storefront
  4. Login to admin area
  5. Go to stores > Configuration > Advanced > Developer > Translate Inline
  6. Set Enabled for Storefront option to Yes and save configuration
  7. Flush Cache
  8. Template strings are shown with formatting when inline translation is enabled.

Expected: Text remains the same
Actual: Text shows formatting characters like {{ }}

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 Feb 9, 2021

Hi @mastiuhin-olexandr. Thank you for your contribution
Here are 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
  13. Semantic Version Checker

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.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

@m2-community-project m2-community-project bot added Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Severity: S4 Affects aesthetics, professional look and feel, “quality” or “usability”. labels Feb 9, 2021
@namlier
Copy link
Contributor Author

namlier commented Feb 10, 2021

@magento run all tests

Comment on lines 264 to 269
if ($translateInline->isAllowed()) {
return $this->inlineSensitiveEscapeHthmlAttr((string) $string);
}

return $this->getEscaper()
->escapeHtmlAttr((string) $string);
Copy link
Member

Choose a reason for hiding this comment

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

Use ternary operator to avoid too much early returns

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Can you, please, confirm that it will look better?

Suggested change
if ($translateInline->isAllowed()) {
return $this->inlineSensitiveEscapeHthmlAttr((string) $string);
}
return $this->getEscaper()
->escapeHtmlAttr((string) $string);
return $translateInline->isAllowed() ?
$this->inlineSensitiveEscapeHthmlAttr($string) :
$this->getEscaper()
->escapeHtmlAttr($string);

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Member

Choose a reason for hiding this comment

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

Yes, like this:

Suggested change
if ($translateInline->isAllowed()) {
return $this->inlineSensitiveEscapeHthmlAttr((string) $string);
}
return $this->getEscaper()
->escapeHtmlAttr((string) $string);
$translateInline = $this->getTranslateInline();
return $translateInline->isAllowed()
? $this->inlineSensitiveEscapeHthmlAttr((string) $string)
: $this->getEscaper()->escapeHtmlAttr((string) $string);

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed.

*/
private function inlineSensitiveEscapeHthmlAttr(string $text): string
{
$escaper = $this->getEscaper();
Copy link
Contributor

Choose a reason for hiding this comment

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

Please check that string has length more or eq 6 before.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thank you, fixed.

* @return void
* @dataProvider escapeHtmlAttrWithInlineProvider
*/
public function testEscapeHtmlAttrWithInline(string $input, string $output): void
Copy link
Contributor

Choose a reason for hiding this comment

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

Please dont contract words. Rename
testEscapeHtmlAttributeWithInlineTranslateEnabled

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed.

*
* @return array
*/
public function escapeHtmlAttrWithInlineProvider(): array
Copy link
Contributor

Choose a reason for hiding this comment

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

Please dont contract words. Rename
escapeHtmlAttributeWithInlineTranslateEnabledDataProvider

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed.

@namlier
Copy link
Contributor Author

namlier commented Feb 15, 2021

@magento run all tests

1 similar comment
@namlier
Copy link
Contributor Author

namlier commented Feb 15, 2021

@magento run all tests

@m2-community-project m2-community-project bot moved this from Changes Requested to Review in Progress in High Priority Pull Requests Dashboard Feb 15, 2021
@dmitriyprime
Copy link
Contributor

✔️ QA passed

Before:
before

After:
after

@engcom-Bravo engcom-Bravo self-assigned this Feb 19, 2021
@engcom-Bravo engcom-Bravo moved this from Ready for Testing to Testing in Progress in High Priority Pull Requests Dashboard Feb 19, 2021
@m2-community-project m2-community-project bot moved this from Testing in Progress to Ready for Testing in High Priority Pull Requests Dashboard Feb 19, 2021
@m2-community-project m2-community-project bot moved this from Ready for Testing to Testing in Progress in High Priority Pull Requests Dashboard Feb 19, 2021
@engcom-Bravo engcom-Bravo removed their assignment Feb 19, 2021
@engcom-Bravo engcom-Bravo moved this from Testing in Progress to Ready for Testing in High Priority Pull Requests Dashboard Feb 19, 2021
@zakdma
Copy link
Contributor

zakdma commented Feb 24, 2021

@magento-engcom-team
Copy link
Contributor

@zakdma, an error occurred during the Pull Request import.

@magento-engcom-team
Copy link
Contributor

@zakdma the branch with code successfully imported intomagento-tsg/magento2ce repository. Branch name: imported-magento-magento2-32002.

@m2-assistant
Copy link

m2-assistant bot commented Mar 3, 2021

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

@@ -3,6 +3,7 @@
* Copyright © Magento, Inc. All rights reserved.
* See COPYING.txt for license details.
*/
declare(strict_types=1);
Copy link
Contributor

Choose a reason for hiding this comment

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

@mastiuhin-olexandr @zakdma,
FYI this change caused a regression #34413.
Please be careful with adding strict_types and not checking all the methods that might be affected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Escaper Component: Test Component: Translation Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Release Line: 2.4 Severity: S4 Affects aesthetics, professional look and feel, “quality” or “usability”.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Invalid Template Strings when Translate Inline enabled
7 participants