Closed Tjitse-E closed 3 years ago
Thanks for your message. We'll look into it!
@woutse great, can't we leave the issue open until this is fixed?
Also noticing the same problem over here. @woutse, this issue should remain open until fixed, right?
It's probably time you start dropping Magento < 2.3 support? Or maybe figure out a better solution then this hack.
Thank for your message. We are working on this!
ready wednesday
This problem should now be solved with the latest release 2.0.0. Can you confirm? Thanks!
Thanks @woutse: I can confirm that the autoload warnings are gone using version 2.0.0 of your module! 🙂
However, I'd advise you to change the constraints in the composer.json
file a bit, since currently you can still install version 2.0.0 on Magento 2.2 using composer I think, I would suggest something like this which should allow Magento 2.3.0 until 2.4.x:
"magento/module-sales": "^102.0.0 || ^103.0.0",
"magento/module-payment": "^100.3.0",
"magento/module-quote": "^101.1.0",
Good to hear! Good point. We'll dig into this as well. I'll keep you informed here.
We investigated this. Changes will be made and available in the next release!
@woutse any updates on this one?
He! In the meantime above, lets say sub-issues, are already fixed! For composer 2.0 compatibilty we are waiting for Magento to approve our latest release.
?? Should Magento approve 3th party extensions?
Approval for Magento marketplace. The plugin is now installable via composer 2.X!
I noticed this message when running
composer dump-autoload --optimize
for one of our projects. Magento 2.4.2 is already compatible with composer 2.0, so it makes sense to fix autoloading in this module.