#1684: Login failed error contains HTML tags

[yolouiese]

Need to verify (*)

• if error messages no longer contain HTML tags
• error messages are rendered as HTML

Description (*)

• added a function to format and render error/success messages as HTML

Fixed Issues (if relevant)

1. Fixes Login failed error contains HTML tags adobe-stock-integration#1684: Login failed error contains HTML tags

Manual testing scenarios (*)

1. Go to Content - Media Gallery, click Search Adobe Stock
2. Save an Unlicensed image Preview
3. (the image appeared in Media Gallery)
4. Select the previously saved Unlicensed image
5. Click "three dots" and select License

Expected result (*)

Proper error message, like "Login failed. Please check if the Secret Key is set correctly and try again."

[m2-assistant]

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

⚠️ 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

[yolouiese]

@magento run all tests

[sivaschenko]

Thanks for the pull request @yolouiese , can you please cover the messages component with jasmine tests

[yolouiese]

@magento run all tests

[yolouiese]

@magento run all tests

[magento-engcom-team]

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

[sivaschenko]

@magento run all tests

[magento-engcom-team]

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

[sivaschenko]

@magento run all tests

[m2-assistant]

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