-
Notifications
You must be signed in to change notification settings - Fork 17
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
Deprecation Notice: Not compatible with Composer v2.0 #33
Comments
Same here. |
Same. |
@tomredhot @abellion I raised a case with Esendex support yesterday - it's pretty apparent that they don't bother with this repository, you may need to do the same :) |
Hello, I'm one of the Esendex platform developers. I've been looking into this issue and I'm unable to reproduce it. First I installed Composer 2.0.7. I created composer.json with the
I was then able to successfully run I created a PHP script and I was then able to instantiate objects from the Esendex SDK with no issues. I have not seen any errors or warnings from Composer. Given this, we're going to need some more information about what kind of project setup leads to the error message you reported, and when do you see it? |
Generate an optimised autoload file, which is standard practice when deploying to production environments.
https://getcomposer.org/doc/03-cli.md#install-i The actual issue is that you are not PSR-0/4 compliant, which prevents the conversion to classmap |
@mwalton-esendex any chance of an update? |
For those who are still waiting for Esendex to fix their legacy SDK, here are some workarounds : |
This has been fixed in the latest release (3.0.0). Sorry for the delay in resolution. |
As it says on the tin.
Class Esendex\AutoLoader located in ./vendor/esendex/sdk/src/autoload.php does not comply with psr-0 autoloading standard. It will not autoload anymore in Composer v2.0.
The text was updated successfully, but these errors were encountered: