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
I have a question about the requirement to use this package?
If this project don't use zendframework and zfcampus packages, is it really necessary add a new dependency?
This Composer plugin, when enabled in a project, intercepts requests to install packages from the zendframework and zfcampus vendors, and will replace them with the equivalents from the Laminas Project.
I understand that is necessary use this package only in projects, not in components, Am I wrong to think like this?
The text was updated successfully, but these errors were encountered:
To remove the plugin, you'd need a new major version, as dependencies that still run with Zend\ symbols crash.
The plugin is designed to ease the Zend\ to Laminas\ migration, and can indeed be dropped now that more people moved over, but it does require a major release to do so.
I understand the obligation to drop only in the major version. But the project started the version 3 on Dec 17, could be possible to start a new major version in the next months?
I started this discussion because I have a conflict between this package and the "aws/aws-sdk-php-zf2". They're using the package "laminas/laminas-dependency-plugin" in the version ^1.0, and someone opened a pull request to remove the package from there.
I have a question about the requirement to use this package?
If this project don't use zendframework and zfcampus packages, is it really necessary add a new dependency?
In the package's README we have this:
I understand that is necessary use this package only in projects, not in components, Am I wrong to think like this?
The text was updated successfully, but these errors were encountered: