-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Cleanup ObjectManager usage - Magento_Bundle #26397
Cleanup ObjectManager usage - Magento_Bundle #26397
Conversation
Hi @Bartlomiejsz. Thank you for your contribution
For more details, please, review the Magento Contributor Guide documentation. |
3de05a6
to
331687e
Compare
2e374b1
to
8274412
Compare
@magento-engcom-team not sure why Unit Tests are marked as failing since there are no failures in Allure report for neither CE, EE or B2B |
8274412
to
f05629f
Compare
f05629f
to
c024c04
Compare
c024c04
to
ec09477
Compare
@magento run Unit Tests |
@Bartlomiejsz I believe it's already ready for review? |
Hi @ihor-sviziev to be honest I'm not sure, I'll try to verify later today if there are any other occurrences to be fixed in this module and will let you know |
ec09477
to
e535d37
Compare
Hi @ihor-sviziev, I added some additional changes, once the tests are passed will be ready for review |
Hi @ihor-sviziev, thank you for the review. |
✔️ QA Passed |
… feature/dependencies_into_constructor_bundle
@magento run all tests |
@magento run Functional Tests B2B, Functional Tests CE, Functional Tests EE |
Failed unit tests not related to the changes in this PR |
Hi @Bartlomiejsz, thank you for your contribution! |
Description (*)
This PR cleanups ObjectManager usage in Magento_Bundle, adds additional dependencies with backward compatibility to api classes, and removes object manager instantiation from non-api classes
Manual testing scenarios (*)
Questions or comments
Contribution checklist (*)