#39353 Added sanitization of address fields for the presence of template variables in the customer address

[rostilos]

Description (*)

Added sanitize for address fields. Added for abstract address model class to avoid template processor handling variables specified directly in the address.
{{ template_var }} -> {{ template_var }}

Related Pull Requests

Fixed Issues (if relevant)

1. Fixes [Address Book Bug] Template filter \Magento\Framework\Filter\Template cannot deal with improper input #39353

Manual testing scenarios (*)

1. When creating or editing an address ( storefront/adminhtml ), enter into any of the address fields a template variable of the following form : {{if city}}{{var city}}, {{/if}}
2. Check if there is a validation error

Questions or comments

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 @rostilos. 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.

[rostilos]

@magento run all tests

[rostilos]

@magento run all tests

[rostilos]

@magento run all tests

[rostilos]

@magento run all tests

[rostilos]

@magento run all tests

[magento-automated-testing]

Pull Requests are not mergeable to the mainline. Please merge the latest mainlines to your Pull Requests and restart the builds.

[rostilos]

@magento run all tests

[rostilos]

@magento run Functional Tests EE, Functional Tests B2B, Functional Tests CE

[rostilos]

I don't see a direct correlation between my edits and errors on most tests.
But I would like to clarify : what should I do to eliminate this error in the tests (which is obviously caused by my edits) ?