Closed alstr closed 3 days ago
If we were to check for multiple matches in languages.yml
, this would potentially add a lot of iterations and complexity. At the moment, custom languages seem the best way to deal with mismatched extensions, as a custom language should take priority over one in languages.yml
.
As highlighted in #163, in some cases a file extension may be associated with multiple languages in
languages.yml
, e.g..cls
.At the moment, the action just finds the first one. It would be good to handle this better, as the first is not necessarily the most relevant.