Skip to content

Conversation

@bartoszherba
Copy link
Collaborator

@bartoszherba bartoszherba commented Jul 1, 2022

Description

  • add proper encoding in the customer order history

Related Issue

Motivation and Context

How Has This Been Tested?

  1. Buy any product with special signs, i. e. "Pursuit Lumaflex™ Tone Band".
  2. Go to "My account" -> "Order history".
  3. Open details of last order.

Screenshots (if appropriate):

Screenshot 2022-07-01 at 08 47 20

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

- add proper encoding in the customer order history
@Frodigo Frodigo added this to the 1.0.0-rc.10 milestone Jul 1, 2022
@Frodigo Frodigo merged commit 6742930 into develop Jul 1, 2022
@Frodigo Frodigo changed the title fix: m2-839. product names with special signs are wrongly encoded fix: product names with special signs are wrongly encoded Jul 4, 2022
@bloodf bloodf deleted the M2-839-my-account-product-names-with-special-signs-are-wrongly-encoded-in-order-history branch December 5, 2022 05:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants