`.yaml` extension not working
krystof-k opened this issue · 4 comments
.standard.yaml and .standard_todo.yaml are not being loaded although .yaml is the official extension.
It would be reasonable to support both .yml and .yaml (and prefer .yaml) extensions to avoid any confusion.
Huh, this thought has never crossed my mind and I'd never considered it.
Does Rails load both .yml and .yaml?
Well, probably not, which means I can create the same issue there too ;) Or another answer may be it depends, as there are references to both .yaml and .yml in the source.
I just spent a few minutes being confused why the config is not used as I'm used to use .yaml, so anyway adding support for both extensions may prevent this.
Regardless of what the website says the preferred extension is, if it turns out that by convention every Ruby library expects .yml, then I'm 👎 on adding a second .yaml just to satisfy some website. At that point, we'd also have to handle the case where both exist, and inevitably somebody would wind up with a config file that "doesn't work", leading to very hard-to-debug support issues.
Well, it's not some website, it's the official website of the YAML standard ;)
However I get it, there kind of is such a convention to use .yml in the Rails world, so it is probably OK to stick with that although I don't see anything wrong to support also .yaml as an option (as most of the tools out there which use YAML do). Fell free to close the issue.