Why `build_config` only support `.yaml` extension not both `.yaml` and `.yml`?

[schaipipat]

Not sure if this is the right place to ask or not, but my background from using many of YAML file, it suppose to recognize that both .yaml and .yml is the extension for the same file type.

[jakemac53]

While those are both common extensions, I don't know that it is common to accept a file with either extension?

In other words, if I wanted to detect if some file was a yaml file, I would look for both extensions. But if I want to accept configuration via a yaml file at a specific path, I don't think it is common to accept two paths, one with either extension. It just isn't worth doing imo and leads to weird differences between projects. Better to have a single convention.

Also a practical matter, in the Dart ecosystem, all tools pretty much use the yaml extension. I am not aware of any that accept either (see pubspec.yaml, dart_test.yaml, build.yaml).

[jakemac53]

One possible solution could be checking for that file, and emitting a warning about it, suggesting that it should probably be renamed to build.yaml? Our other tools don't do this though.

[schaipipat]

May be a good thing to have for people who just come from another languages/tools like me. I'm happy to contribute if you're busy. Thanks a lot. 🙇‍♂️

[jakemac53]

I do know of one other person who also made this mistake so you definitely aren't alone :)

[jakemac53]

I do feel quite comfortable adding a check in for that file and emitting a warning. We can still keep a consistent convention that way and it doesn't promise any kind of long term support or maintenance burden, it would be a nice isolated piece of code.