Unnecessarly escaped charaters in ProductInterface

[cornedor]

Preconditions and environment

• Magento version 2.4.8-p1

5c6d83d

This change produced unnecessary and unreliable escaped product names in GraphQL responses. The GraphQL endpoint should never return escaped values for several reasons:

1. Not every platform works with HTML entities, this prevents names from being rendered correctly in native apps.
2. The rest of the GraphQL API does not returned escaped variables. This gives developers a false sense of security, and could introduce real security issues when a developer assumes this happens everywhere.
3. This was a breaking change.

Steps to reproduce

1. In Magento admin, create a product with a special character in the name. For example >.
2. Query the name from that product using GraphQL.

Expected result

It should return unescaped > in the name.

Actual result

The GraphQL API returns the escaped greater than sign >

Additional information

No response

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @cornedor. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues 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 issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-November. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-November]

Hello @cornedor

We attempted to reproduce the issue in the latest 2.4-develop by following the provided steps. We are able to reproduce the issue. Please refer to the attached screenshot for details.

Steps to Reproduce:

• In Magento admin, create a product with a special character in the name. For example >.
• Query the name from that product using GraphQL.

We followed the preconditions and steps as provided and encountered the issue. Therefore, we are marking this ticket as "Issue: Confirmed."

We appreciate you bringing this to our attention. If you have a proposed fix, we’d love for you to submit a pull request—your contributions help strengthen Magento Open Source for the entire community. If you need any support along the way, please feel free to reach out!

Thank you again!

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-15494 is successfully created for this GitHub issue.