-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drastically simplify using Composer Runtime API #64
Conversation
This PR was motivated by DrupalFinder not working at ddev/ddev-drupal-contrib#14 (composer.json not customized, on purpose) |
I was converging on this, as well, for phpstan-drupal. I think it's safe to say everyone is on the correct version of Composer, which added this. It's been two or three years, maybe more? It'd be great to have this merged and kick off the 2.x of the package. |
I have extended the test coverage and added support for custom vendor-dir. This is rarely used, but we should nevertheless have it supported. Added a test-case for "default" Drupal with customized path in extra.installer-paths. |
Are there more obscure test cases? |
I think this is OK. Custom vendor directory should automatically be handled in the compiled runtime data, as Composer installed its information there. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks even better. Thanks Webflo.
The README file needs work. The purpose of this library has changed with this PR. It no longer uses the "current path" or filesystem. I was wondering if we should keep the old |
I personally would recommend the 1.x branch for non composer tools. |
Updated README. |
|
Hit this while trying to add |
Merged #65 instead |
I think this is all thats needed now that Composer provides a Runtime API to get the paths we want.