Add support for .editorconfig
file extension
#6156
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
There appears to be ample usage of
.editorconfig
as a legitimate file extension, rather than a complete filename. This PR adds it as an extension to EditorConfig's language entry.Sidenotes
My initial approach was this…
… however,
test_samples.rb
got confused by the EditorConfig sample named.editorconfig
(which ostensibly doesn't equate to a filename containing only an extension):@lildude, please let me know if this is correct behaviour; if so, I'll stick with the less-than-D.R.Y approach I resorted to for this PR. 😉
Checklist
Code Search yields ~39,000 results for
path:**/?*.editorconfig
.NB: The latter sample was edited to eliminate a lot of repetitive and excessive data.
ASP.NET.EditorConfig
]: Source | MIT-licensedIntelliJ.editorconfig
]: Source | Apache-2.0I have included a change to the heuristics