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
Currently, If you were to add a new major version to a root/framework package where your directory structure changed, your packages supporting that framework cannot specify the version of the package they support.
The best "workaround" is currently to override the framework name in your root package config for the new version. This means that no new root package repository would be needed and your child packages can simply add the new framework name to their map.
I think the solution above is probably adequate, but we should at least explore the idea of specifying project/framework versions in the child package. It's most likely possible to take advantage of the functionality provided by \Composer\Package\Version\VersionParser in supporting this.
The text was updated successfully, but these errors were encountered:
Currently, If you were to add a new major version to a root/framework package where your directory structure changed, your packages supporting that framework cannot specify the version of the package they support.
The best "workaround" is currently to override the framework name in your root package config for the new version. This means that no new root package repository would be needed and your child packages can simply add the new framework name to their map.
I think the solution above is probably adequate, but we should at least explore the idea of specifying project/framework versions in the child package. It's most likely possible to take advantage of the functionality provided by
\Composer\Package\Version\VersionParser
in supporting this.The text was updated successfully, but these errors were encountered: