Fix incorrect condition check and method name typo for \Magento\Framework\Escaper

[wubinworks]

Fixed incorrect condition check and method name typo for \Magento\Framework\Escaper.

Description (*)

• Fixed incorrect condition check in \Magento\Framework\Escaper::escapeScriptIdentifiers
• Fixed \Magento\Framework\Escaper::inlineSensitiveEscapeHthmlAttr method name typo

Related Pull Requests

N/A

Fixed Issues (if relevant)

1. Fixes Condition is never met in \Magento\Framework\Escaper::escapeScriptIdentifiers #40195

Manual testing scenarios (*)

N/A

Questions or comments

If you care about the unit test, it is not possible to let preg_replace return NULL with the given valid regular expression here and here.

The check for NULL is just a "safeguard".

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)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @wubinworks. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.
❗ 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
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

---

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

[ct-prd-pr-scan]

The security team has been informed about this pull request due to the presence of risky security keywords. For security vulnerability reports, please visit Adobe's vulnerability disclosure program on HackerOne or email [email protected].

[wubinworks]

@magento run all tests