This PR will move the plugin dependencies vendor directory to wp-content/vendor.
It will change the install behaviour a bit, so it can install the dependencies in a complete separate routine and separate composer.json file (plugins-composer.json actually).
This needs to run the installer twice actually, the second time without a plugins-composer.lock file that will be generated after running the first installer on plugins-composer.json. The first will install the wikimedia/composer-merge-plugin package, while the second will run the merge and install all the dependencies of all the hooked in plugins.
The first installer can run on activation of this WordPress plugin, the second as initial setup step maybe? It will need to run again and again after a plugin has been activated or deactivated, so it can resolve the dependencies again to make sure the right dependencies are available.
Todo before this is ready to merge:
[x] Update README.md file with new flow introduced in this PR.
This PR will move the plugin dependencies vendor directory to
wp-content/vendor.It will change the install behaviour a bit, so it can install the dependencies in a complete separate routine and separate
composer.jsonfile (plugins-composer.jsonactually).This needs to run the installer twice actually, the second time without a
plugins-composer.lockfile that will be generated after running the first installer onplugins-composer.json. The first will install thewikimedia/composer-merge-pluginpackage, while the second will run the merge and install all the dependencies of all the hooked in plugins.The first installer can run on activation of this WordPress plugin, the second as initial setup step maybe? It will need to run again and again after a plugin has been activated or deactivated, so it can resolve the dependencies again to make sure the right dependencies are available.
Todo before this is ready to merge:
README.mdfile with new flow introduced in this PR.