-
Notifications
You must be signed in to change notification settings - Fork 6
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
Drop support for behat/mink-extension in favor of friends-of-behat/mink-extension #78
Comments
Hey @robertfausk , Thanks for raising this. I'll give this a go soon. I'd appreciate a pull request if you can raise one. It would be ace if the replacement worked out. For BC the other versions are still out there that can be used. Related issue on behat/mink-extension Behat/MinkExtension#370 |
Question: Is the travis build still working?
It seems that the https://stackoverflow.com/questions/18882201/how-does-the-replace-property-work-with-composer |
Travis does work, best way to find out I guess is to push a change up. It may be an access related thing or the link may have changed since this last ran (10 months ago). I don't mind a github actions PR if you'd like to push one in (even if travis still runs on the side) just to see how GHA works out compared to Travis. The friendsofBehat repo doesn't have an official stand point i.e it doesn't say that it replaces the old one neither is the old one abandoned - i'll dig a bit further to see what needs doing soon. Thanks for raising this. |
Any updates on this? Not sure which package is responsible, but I'm now running into the "Ambiguous class resolution" described here: Behat/MinkExtension#370 FYI, latest releases for drupal/drupal-extension aka https://github.com/jhedstrom/drupalextension and dmore/behat-chrome-extension aka https://gitlab.com/behat-chrome/behat-chrome-extension have switched to using the friends-of-behat package. |
@aaronbauman thanks for reporting. Can you run the commands in verboae mode and dump the output here? Also what steps and commands have you executed to get this issue? |
Here's are the packages that (i think) create the conflict:
And here's the full
|
I resolved this by explicitly updating the
which should pull in the "replace" from the composer.json file linked. Output:
|
@aaronbauman its a bit late, but does the above solution work for you? The friends of behat repo does not have an official stand point (well they do which isn't very encouraging) hence I am reluctant on the change unless the old one gets abandoned. |
@robertfausk thanks for your comment from awhile - it made me look at travis CI and indeed they've moved to a payment plan model since. Will fix this soon. |
composer install works now, thanks. behat jobs are still failing, but i don't think it's this package that's causing the failure. |
What is the issue?
I can not upgrade to Symfony 5.x respectively I have two versions of
mink-extension
installed.How did it happen?
https://github.com/Behat/MinkExtension is outdated (last release on 5 Mar 2018).
As a drop in replacement https://github.com/FriendsOfBehat/MinkExtension can be used.
What should have happened?
behat-fail-aid
automatically usesfriends-of-behat/mink-extension
instead ofbehat/mink-extension
.I do not know if there is an easy way to support both librarys without introducing a BC.
The text was updated successfully, but these errors were encountered: