Consistently use yml instead of yaml extension in documentation #824
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.
Even though I can see that grumphp allows for both yml and yaml configuration files like it is supposed to:
grumphp/src/Locator/GuessedPathsLocator.php
Lines 109 to 112 in 0e6287a
I think semantically it's best to stay consistent through out the documentation to only reference one of the allowed extensions. A quick search showed that yml was the prefered extension:
This pull request changes the extension in the documentation only. No code is touched. Maybe we could document that the GuessedPathsLocator allows for both yml and yaml extension on the grumphp configuration files. I just don't really know where to put that.