yml vs yaml #219
-
It seems the community is split between using the Searching for The official YAML FAQ states:
This has been the recommendation for yaml files since September of 2006. The main argument for using |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
"however the publiccode.yml file does not adhere to this rule" |
Beta Was this translation helpful? Give feedback.
-
So what will be the conclusion of this discussion? 😇 |
Beta Was this translation helpful? Give feedback.
-
Thanks for raising the issue @EmilMagenta, it’s kind of funny that no one pointed it out before 😄 I actually agree we should support both .yml and .yaml. Technically, only .yml is correct for publiccode files and matches the project name as @jgroenen said, but as you said people are already using .yaml in some repos and it's actually a pretty reasonable assumption for users to think .yaml would work. It's not a big effort for the crawler to check both extensions. We could prioritize .yml for consistency and backward compatibility (for example, if they both exist in the same repo), but still handle .yaml as a valid option. |
Beta Was this translation helpful? Give feedback.
Thanks for raising the issue @EmilMagenta, it’s kind of funny that no one pointed it out before 😄
I actually agree we should support both .yml and .yaml.
Technically, only .yml is correct for publiccode files and matches the project name as @jgroenen said, but as you said people are already using .yaml in some repos and it's actually a pretty reasonable assumption for users to think .yaml would work. It's not a big effort for the crawler to check both extensions.
We could prioritize .yml for consistency and backward compatibility (for example, if they both exist in the same repo), but still handle .yaml as a valid option.