You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Beginning with Composer 2.0, classes that do not comply with the PSR-4 naming standard are not autoloaded.
When I try to use this package with Composer 2.0, it shows this warning:
Class org\nameapi\client\fault\HttpResponseData located in ./vendor/optimaize/nameapi-client-php/src/org/nameapi/client/http/HttpResponseData.php does not comply with psr-4 autoloading standard. Skipping.
Class org\nameapi\client\services\riskdetector\riskdetector\PersonRiskDetectorService located in ./vendor/optimaize/nameapi-client-php/src/org/nameapi/client/services/riskdetector/person/PersonRiskDetectorService.php does not comply with psr-4 autoloading standard. Skipping.
This article does a good job explaining that the folder names need to start with uppercase letters.
I will try to fork the library and submit a PR soon unless this change is already under development?
The text was updated successfully, but these errors were encountered:
@mstralka Thank you for opening this issue, we are waiting for this as well as we're also planning on upgrading to Composer 2.0.
Hopefully the dev will answer soon.
Beginning with Composer 2.0, classes that do not comply with the PSR-4 naming standard are not autoloaded.
When I try to use this package with Composer 2.0, it shows this warning:
This article does a good job explaining that the folder names need to start with uppercase letters.
I will try to fork the library and submit a PR soon unless this change is already under development?
The text was updated successfully, but these errors were encountered: