Open akrillo89 opened 7 years ago
Indentation in general is flaky I find, If i want to do this:
//Comment title ----//Comment sub title ----//Comment content
OR //reds $red: #ff0000; ----$cotton-candy: #ffc0ff; ----$dark-tan: #5F0808; ----$guardsman-red: #bf0b0b; ----$your-pink: #f7bbbb;
//blues $blue: #0000ff; ----$cerulean-blue: #0b50bf; ---- $light-cyan: #c0ffff; ----$pattens-blue: #d1ebf7; ----$torea-bay: #022896;
It totally freaks out saying it found 8 spaces when 0 were expected or the like. We need to do this so things are organised to the eye, it only expects tabbing inside a function, mixin, declaration block in other words.
Sorry, don't mean to hijack your post, was just backing you up on stating indenting is a bit off.
what is the current state of this project? Are there still active maintainer?
We've been quiet for a while, everyone involved recently changed jobs or moved house etc so it's been a busy time. Will look into getting more activity in the coming weeks. This issue has already been discussed elsewhere and is just a missing case in the indentation rule which for a long time has needed a bit of an overhaul but due to the state of the AST we were using that task wasn't going to be worth much as the format has changed slightly in their V4.
Will look to revive this once the V4 update of our AST is released.
Hey,
right now the comments have issues with line indentation validation. For example when I use the linter for the following definition:
I get an issue in line 14. It's best practice to put a comment above a definition to avoid long lines.
I am using sass lint via command line and in visual code. Both have the same error.
sass-lint version: 1.10.2
.sass-lint.yml