-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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.
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
Update Framework interfaces and mark as API #32142
Update Framework interfaces and mark as API #32142
Conversation
Hi @mrtuvn. Thank you for your contribution
❗ Automated tests can be triggered manually with an appropriate comment:
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. 🕙 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 |
@@ -105,6 +105,7 @@ public function __construct( | |||
* | |||
* @param string $area | |||
* @return $this | |||
* @deprecated | |||
*/ | |||
public function setArea($area) | |||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sivaschenko @sidolov @gabrieldagama should we safe for remove this method ? Method defined in interface already removed but i just think we should keep method here for backward compatible
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In my opinion we should clear legacy code in major release
172f8a0
to
ebaed95
Compare
ebaed95
to
554149f
Compare
@magento run all tests |
554149f
to
1858976
Compare
@magento run Integration Tests, Static Tests, Unit Tests, Functional Tests B2B, Functional Tests CE, Functional Tests EE |
de18fa6
to
cf423f3
Compare
@magento run all tests |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time. |
@magento run all tests |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time. |
@magento run all tests |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time. |
@magento run all tests |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time. |
Description (*)
Mark following interfaces as API + removed deprecated methods usage in code base + added declare strict_types
Update integration tests coverage with changes
lib/internal/Magento/Framework/App/Config/ValueInterface.php @api
lib/internal/Magento/Framework/MessageQueue/ConsumerConfigurationInterface.php @api + remove deprecated method
lib/internal/Magento/Framework/View/DesignInterface.php mark @api + remove deprecated method setArea from interface
lib/internal/Magento/Framework/Webapi/CustomAttributeTypeLocatorInterface.php @api + remove deprecated method
Related Pull Requests
Fixed Issues (if relevant)
Manual testing scenarios (*)
Questions or comments
CC: @ihor-sviziev @sivaschenko @kandy @pauliarush
Contribution checklist (*)