Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This addition serves two purposes: 1. It helps to enforce consistent formatting in editors that support the EditorConfig format. This reduces the odds that a contributor submits a change that deviates from existing code-style. 2. It improves the display of tabs on GitHub.com, which is notorious for being hostile towards users who prefer tabs instead of spaces (a.k.a, the logical and superior method of indenting source code). As a kludge, GitHub's devs added an admittedly-buggy enhancement that scales the width of tab characters to the local `indent_size` setting configured in a repository's `.editorconfig` file. This approach is imperfect, and goes against the principles of proper tab-use; i.e., semantic indentation, described in the style-guides of Go, jQuery, WordPress and other projects that care about readability. Consult the URL below for a more in-depth discussion of this matter. http://github.com/isaacs/github/issues/170#issuecomment-590214226 The `default_only` field is a non-standard property that, eventually, will enable authors to configure a GitHub project's default tab-width without forcing the setting upon those working with code locally. The EditorConfig spec permits extensions in the form of new properties so this isn't strictly illegal. The `elastic_tabstops` property is also non-standard, but the feature it references is well-specified and likely to be supported by certain EditorConfig implementations (though I currently know of none). Spec: https://nickgravgaard.com/elastic-tabstops/
- Loading branch information