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've made some research how to decrease linking customisation.
Composer already support linking but it makes us add the repositories section into each package and handle it in the right way if we use or not yii-dev-tool. So basically we can create a plugin that will add the repositories section at runtime and link packages if they are present locally.
I've developed this plugin and it works easy:
At installation step it collects each packages that the composer.json contains in addition to they versions.
Registers "in-memory repository" that will provide that packages, but refer to their local versions.
The rest process is the same as we added the repositories section into composer.json.
The installation process is also easy:
composer req yiisoft/yii-dev-tool-installer. It's is not registered in packagist.org and you may face with error.
Allow it in composer.jsonconfig.allow-plugins section:
I've made some research how to decrease linking customisation.
Composer already support linking but it makes us add the
repositories
section into each package and handle it in the right way if we use or notyii-dev-tool
. So basically we can create a plugin that will add therepositories
section at runtime and link packages if they are present locally.I've developed this plugin and it works easy:
composer.json
contains in addition to they versions.The rest process is the same as we added the
repositories
section intocomposer.json
.The installation process is also easy:
composer req yiisoft/yii-dev-tool-installer
. It's is not registered in packagist.org and you may face with error.composer.json
config.allow-plugins
section:Here is the plugin: https://github.com/xepozz/yii-dev-tool-installer/blob/master/src/InstallerPlugin.php.
Advantages:
@yiisoft/yii3 I'd like to hear your opinions.
The text was updated successfully, but these errors were encountered: