Mark Framework interfaces as API part 9

[sivaschenko]

The following interfaces should be marked as API in 2.4-develop branch

1. lib/internal/Magento/Framework/View/File/FileList/CollateInterface.php
2. lib/internal/Magento/Framework/View/Helper/SecureHtmlRender/SecurityProcessorInterface.php
3. lib/internal/Magento/Framework/View/Layout/Argument/UpdaterInterface.php
4. lib/internal/Magento/Framework/View/Layout/Condition/VisibilityConditionInterface.php
5. lib/internal/Magento/Framework/View/Layout/GeneratorInterface.php
6. lib/internal/Magento/Framework/View/Layout/LayoutCacheKeyInterface.php
7. lib/internal/Magento/Framework/View/Layout/ProcessorInterface.php
8. lib/internal/Magento/Framework/View/Layout/ReaderInterface.php
9. lib/internal/Magento/Framework/View/Model/PageLayout/Config/BuilderInterface.php
10. lib/internal/Magento/Framework/View/Page/Config/RendererInterface.php
11. lib/internal/Magento/Framework/View/TemplateEngine/Xhtml/Compiler/AttributeInterface.php
12. lib/internal/Magento/Framework/View/TemplateEngine/Xhtml/Compiler/CdataInterface.php
13. lib/internal/Magento/Framework/View/TemplateEngine/Xhtml/Compiler/CommentInterface.php
14. lib/internal/Magento/Framework/View/TemplateEngine/Xhtml/Compiler/Directive/DirectiveInterface.php
15. lib/internal/Magento/Framework/View/TemplateEngine/Xhtml/Compiler/Element/ElementInterface.php
16. lib/internal/Magento/Framework/View/TemplateEngine/Xhtml/Compiler/TextInterface.php
17. lib/internal/Magento/Framework/View/TemplateEngine/Xhtml/ResultInterface.php
18. lib/internal/Magento/Framework/View/TemplateEngineInterface.php
19. lib/internal/Magento/Framework/View/Xsd/Media/TypeDataExtractorInterface.php
20. lib/internal/Magento/Framework/Webapi/CustomAttribute/PreprocessorInterface.php
21. lib/internal/Magento/Framework/Webapi/CustomAttribute/ServiceTypeListInterface.php
22. lib/internal/Magento/Framework/Webapi/Rest/Request/DeserializerInterface.php

[m2-assistant]

Hi @sivaschenko. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• 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, 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

[mrtuvn]

@magento i am working on this

[magento-engcom-team]

✅ Confirmed by @engcom-Oscar
Thank you for verifying the issue. Based on the provided information internal tickets MC-41814 were created

Issue Available: @engcom-Oscar, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[magento-engcom-team]

Unfortunately, we are archiving this ticket now as it did not get much attention from both Magento Community and Core developers for an extended period. This is done in an effort to create a quality, community-driven backlog which will allow us to allocate the required attention more easily.

Please feel free to comment or reopen according to the Issue reporting guidelines
the ticket if you are still facing this issue on the latest 2.x-develop branch. Thank you for collaboration.