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
Hi there, I was wondering if it would be possible to remove DrupalFinder as it doesn't seem to really work in most cases on finding the proper Drupal root and causes quite a few problems.
However most notably as soon as you use a distribution or anything else that has installer-paths it will assume that that is the root and then the full test suite will fail.
The dependency on DrupalFinder was introduced recently in #628.
For us it makes sense to use DrupalFinder rather than implement our own discovery mechanism. It is the standard way to find the root of a Drupal installation and the location of the vendor folder. Is very widely used (26 million installs) and since it is a hard dependency of Drush it can be found on the vast majority of Drupal projects.
The library is not perfect, and from the issues you linked it is clear that it is affected by some bugs that prevent the correct location from being found.
Would it be in any way possible to get these issues fixed upstream in the DrupalFinder project itself?
Thank you for the considered response I didn't even realize it was part of Drush.
For now I just reverted to 5.0.0-alpha1 and it allowed my behat tests to run successfully.
I'll look at the issues over in DrupalFinder and see if can find a way to ideally provide an override where you can specify the docroot path if there are competing composer.json files!
Hi there, I was wondering if it would be possible to remove DrupalFinder as it doesn't seem to really work in most cases on finding the proper Drupal root and causes quite a few problems.
You can see all of the issues here:
However most notably as soon as you use a distribution or anything else that has installer-paths it will assume that that is the root and then the full test suite will fail.
The text was updated successfully, but these errors were encountered: