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 Framework Api interfaces #8 #32070

Merged
merged 1 commit into from
Apr 13, 2021
Merged

Mark Framework Api interfaces #8 #32070

merged 1 commit into from
Apr 13, 2021

Conversation

mrtuvn
Copy link
Contributor

@mrtuvn mrtuvn commented Feb 10, 2021 •
edited
Loading

Description (*)

Following interfaces marked as API

lib/internal/Magento/Framework/View/Element/ComponentVisibilityInterface.php
lib/internal/Magento/Framework/View/Element/Message/InterpretationStrategyInterface.php
lib/internal/Magento/Framework/View/Element/Message/Renderer/PoolInterface.php
lib/internal/Magento/Framework/View/Element/Message/Renderer/RendererInterface.php
lib/internal/Magento/Framework/View/Element/UiComponent/BlockWrapperInterface.php
lib/internal/Magento/Framework/View/Element/UiComponent/Config/DomMergerInterface.php
lib/internal/Magento/Framework/View/Element/UiComponent/Config/FileCollectorInterface.php
lib/internal/Magento/Framework/View/Element/UiComponent/Config/UiReaderInterface.php
lib/internal/Magento/Framework/View/Element/UiComponent/ContainerInterface.php
lib/internal/Magento/Framework/View/Element/UiComponent/ContentType/ContentTypeInterface.php
lib/internal/Magento/Framework/View/Element/UiComponent/ContextInterface.php
lib/internal/Magento/Framework/View/Element/UiComponent/Control/ActionPoolInterface.php
lib/internal/Magento/Framework/View/Element/UiComponent/Control/ButtonProviderInterface.php
lib/internal/Magento/Framework/View/Element/UiComponent/Control/ControlInterface.php
lib/internal/Magento/Framework/View/Element/UiComponent/DataProvider/FilterApplierInterface.php
lib/internal/Magento/Framework/View/Element/UiComponent/DataSourceInterface.php
lib/internal/Magento/Framework/View/Element/UiComponent/Factory/ComponentFactoryInterface.php
lib/internal/Magento/Framework/View/Element/UiComponent/JsConfigInterface.php
lib/internal/Magento/Framework/View/Element/UiComponent/LayoutInterface.php
lib/internal/Magento/Framework/View/Element/UiComponent/ObserverInterface.php
lib/internal/Magento/Framework/View/Element/UiComponent/PoolInterface.php
lib/internal/Magento/Framework/View/Element/UiComponent/SubjectInterface.php

Related Pull Requests

Fixed Issues (if relevant)

  1. Fixes Mark Framework interfaces as API part 8 #32035

Manual testing scenarios (*)

  1. ...
  2. ...

Questions or comments

CC: @sivaschenko

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 @mrtuvn. 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
@mrtuvn mrtuvn changed the base branch from 2.4-develop to 2.5-develop February 10, 2021 05:14
@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

@mrtuvn mrtuvn force-pushed the api-interfaces-mark-8 branch from f873906 to b2f87ac Compare February 11, 2021 08:32
@ihor-sviziev
Copy link
Contributor

@magento run all tests

@mrtuvn
Copy link
Contributor Author

mrtuvn commented Feb 13, 2021

@magento run WebAPI Tests, Database Compare

@ihor-sviziev
Copy link
Contributor

@magento run Database Compare

@gabrieldagama gabrieldagama changed the base branch from 2.4-develop to 2.5-develop April 13, 2021 10:01
@gabrieldagama
Copy link
Contributor

@magento import code to https://github.com/magento-engcom/magento2ce

@magento-engcom-team
Copy link
Contributor

@gabrieldagama the branch with code successfully imported intomagento-engcom/magento2ce repository. Branch name: imported-magento-magento2-32070.

@gabrieldagama gabrieldagama changed the base branch from 2.5-develop to api-changes-develop April 13, 2021 13:14
@magento-cicd2 magento-cicd2 merged commit 382c055 into magento:api-changes-develop Apr 13, 2021
@m2-assistant
Copy link

m2-assistant bot commented Apr 13, 2021

Hi @mrtuvn, 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

@engcom-Foxtrot engcom-Foxtrot

Labels
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests Component: Authorization Component: AwsS Component: Backend Component: Bundle Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: ready for testing Project: API Changes QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Mark Framework interfaces as API part 8
7 participants
@mrtuvn @ihor-sviziev @magento-engcom-team @gabrieldagama @magento-cicd2 @engcom-Foxtrot @engcom-Oscar