You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 4, 2020. It is now read-only.
My comment was about comment blocks (😉 ) that were being flagged in your example. There are 3 editorconfig settings that deal specifically with comment blocks, that are separate from the indent settings.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1. Summary
It would be nice, if
eclint fix
will remove leading spaces for tabs users.2. Argumentation
Some tools automatically generate files with leading spaces.
eclint fix
doesn't fix it andeclint check
makes my builds failed.3. MCVE
.editorconfig
— I prefer tabs:KiraECLint.styl
— see Comment-Snippets issue for details:KiraECLint.js
— beginning of real file, that generate by grunt-modernizr:Leading spaces in
KiraECLint.styl
andKiraECLint.js
.4. Steps to reproduce
5. Expected behavior
Remove leading spaces after
fix
, successfulcheck
.6. Actual behavior
Thanks.
The text was updated successfully, but these errors were encountered: