Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Many common tools (phpunit, phpstan, php-cs-fixer) use config files like
<toolname>.<ext>
. To ease collaboration, they and Behat support checking for and using<toolname>.<ext>.dist
.However, those tools also support the
<toolname>.dist.<ext>
, which is arguably superior when it comes to extension conventions (e.g. IDEs need to be thought that.<ext>.dist
is really of type.<ext>
). This PR adds support for that to Behat too.On a sidenote: none of those alternatives are mentioned in any Behat documentation - it seems to be limited to
behat.yml
.