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:
11 results in 6 files for grumphp.yaml
148 results in 71 files for grumphp.yml
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.
Thanks! Makes sense to make it consistent. There isn't really a preferred extension at the moment.
So it's ok to stick with .yml, since it is the first in the list and will be autocreated by GrumPHP.
Even though I can see that grumphp allows for both yml and yaml configuration files like it is supposed to:
https://github.com/phpro/grumphp/blob/0e6287a3ae70a8730d11a239449e991b3fc78f99/src/Locator/GuessedPathsLocator.php#L109-L112
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.