The ArcanistTextLinter is great, except that it is biased in that it cannot be (easily) configured to selectively apply rules to files. It would be a more powerful tool if it read (and understood) .editorconfig files.
This would involve a couple of parts:
- Providing a function for converting glob patterns into regular expressions. Whilst PHP has support for checking glob patterns against a path (namely the fnmatch function), I expect that there are subtle differences in how PHP handles globs compared with the EditorConfig format.
- Providing an EditorConfig parser, probably in libphutil. This would essentially be a light wrapper around parse_ini_file with some validation.
- Modifying the ArcanistTextLinter to take .editorconfig files into account.