Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Mark Catalog interfaces as API #32093

Closed
wants to merge 2 commits into from
Closed

Mark Catalog interfaces as API #32093

wants to merge 2 commits into from

Conversation

vlmed
Copy link
Contributor

@vlmed vlmed commented Feb 10, 2021 •
edited
Loading

Description (*)

The following interfaces marked as API:

  1. app/code/Magento/Catalog/Block/Product/AwareInterface.php
  2. app/code/Magento/Catalog/Block/Product/ReviewRendererInterface.php
  3. app/code/Magento/Catalog/Controller/Adminhtml/Product/Initialization/Helper/HandlerInterface.php
  4. app/code/Magento/Catalog/Controller/Product/View/ViewInterface.php
  5. app/code/Magento/Catalog/Model/Attribute/LockValidatorInterface.php
  6. app/code/Magento/Catalog/Model/Config/Source/ProductPriceOptionsInterface.php
  7. app/code/Magento/Catalog/Model/Entity/Product/Attribute/Group/AttributeMapperInterface.php
  8. app/code/Magento/Catalog/Model/Indexer/Product/Flat/TableDataInterface.php
  9. app/code/Magento/Catalog/Model/Layer/CollectionFilterInterface.php
  10. app/code/Magento/Catalog/Model/Layer/FilterableAttributeListInterface.php
  11. app/code/Magento/Catalog/Model/Layer/ItemCollectionProviderInterface.php
  12. app/code/Magento/Catalog/Model/Layer/StateKeyInterface.php
  13. app/code/Magento/Catalog/Model/Product/Condition/ConditionInterface.php
  14. app/code/Magento/Catalog/Model/Product/Configuration/Item/Option/OptionInterface.php
  15. app/code/Magento/Catalog/Model/Product/Media/ConfigInterface.php
  16. app/code/Magento/Catalog/Model/Product/Pricing/Renderer/SalableResolverInterface.php
  17. app/code/Magento/Catalog/Model/ProductLink/CollectionProviderInterface.php
  18. app/code/Magento/Catalog/Model/ProductLink/Converter/ConverterInterface.php
  19. app/code/Magento/Catalog/Model/ProductLink/Data/ListCriteriaInterface.php
  20. app/code/Magento/Catalog/Model/ProductLink/Data/ListResultInterface.php
  21. app/code/Magento/Catalog/Model/ProductLink/MapProviderInterface.php
  22. app/code/Magento/Catalog/Model/ProductOptions/ConfigInterface.php
  23. app/code/Magento/Catalog/Model/ResourceModel/Product/Indexer/Price/PriceModifierInterface.php
  24. app/code/Magento/Catalog/Model/ResourceModel/Product/LinkedProductSelectBuilderInterface.php
  25. app/code/Magento/Catalog/Pricing/Price/ConfiguredPriceInterface.php
  26. app/code/Magento/Catalog/Pricing/Price/MinimalPriceCalculatorInterface.php
  27. app/code/Magento/Catalog/Pricing/Price/SpecialPriceInterface.php
  28. app/code/Magento/Catalog/Ui/DataProvider/Product/Form/Modifier/Eav/WysiwygConfigDataProcessorInterface.php

Marked as API to fix static test
29. app/code/Magento/Catalog/Model/ResourceModel/Product/Indexer/Price/IndexTableStructure.php

Fixed Issues (if relevant)

  1. Fixes Mark Catalog interfaces as API #32014

Questions or comments

@coderimus

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)
  • All automated tests passed successfully (all builds are green)

@m2-assistant
Copy link

m2-assistant bot commented Feb 10, 2021

Hi @vlmed. Thank you for your contribution
Here are 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
  13. Semantic Version Checker

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

@m2-community-project m2-community-project bot added the Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. label Feb 10, 2021
@magento-engcom-team magento-engcom-team added Release Line: 2.4 Partner: Atwix Pull Request is created by partner Atwix partners-contribution Pull Request is created by Magento Partner labels Feb 10, 2021
@vlmed vlmed changed the base branch from 2.4-develop to 2.5-develop February 10, 2021 13:43
@gabrieldagama gabrieldagama added this to the 2.5 milestone Feb 10, 2021
@ihor-sviziev ihor-sviziev self-assigned this Feb 10, 2021
@ihor-sviziev
Copy link
Contributor

@magento run all tests

@ihor-sviziev ihor-sviziev added the Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests label Feb 10, 2021
@vlmed vlmed force-pushed the mark_as_api_catalog_interfaces branch from 2f6e7c7 to afc3141 Compare February 11, 2021 09:11
@vlmed
Copy link
Contributor Author

vlmed commented Feb 11, 2021

@ihor-sviziev I have removed @since according to comment #32085 (review) in my another pull request with similar issue

@ihor-sviziev
Copy link
Contributor

@magento run all tests

@ihor-sviziev
Copy link
Contributor

ihor-sviziev commented Feb 17, 2021 •
edited
Loading

@magento run Unit Tests, Static Tests, Functional Tests B2B, Functional Tests CE

@ihor-sviziev
Copy link
Contributor

@sivaschenko any thoughs why static tests are failing?

@ihor-sviziev
Copy link
Contributor

@magento run Functional Tests B2B, Integration Tests

@magento-engcom-team
Copy link
Contributor

Hi @ihor-sviziev, thank you for the review.
ENGCOM-8811 has been created to process this Pull Request

@ihor-sviziev
Copy link
Contributor

@magento run Functional Tests B2B

@vlmed vlmed mentioned this pull request Apr 2, 2021
Merged
4 tasks
@gabrieldagama
Copy link
Contributor

Closed in favour of #32659

@m2-assistant
Copy link

m2-assistant bot commented Apr 6, 2021

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ihor-sviziev ihor-sviziev ihor-sviziev approved these changes

Assignees

@ihor-sviziev ihor-sviziev

Labels
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests Component: Catalog Partner: Atwix Pull Request is created by partner Atwix partners-contribution Pull Request is created by Magento Partner Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Release Line: 2.5
Projects
None yet
Milestone
2.5
Development

Successfully merging this pull request may close these issues.

Mark Catalog interfaces as API
5 participants
@vlmed @ihor-sviziev @sivaschenko @magento-engcom-team @gabrieldagama