Skip to content
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

Remove DrupalFinder #652

Closed
sylus opened this issue Jun 26, 2023 · 2 comments
Closed

Remove DrupalFinder #652

sylus opened this issue Jun 26, 2023 · 2 comments

Comments

@sylus
Copy link

sylus commented Jun 26, 2023

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.

@pfrenssen
Copy link
Collaborator

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?

@sylus
Copy link
Author

sylus commented Jun 27, 2023

Yeah that makes sense to me ^_^

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!

@sylus sylus closed this as completed Jun 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants