With great joy I saw the csslint-ignore-block and csslint-allow-line features were merged recently (I've been cherrypicking them both for personal use since they were PR-ed). It would be nice if we could also have multiline allow-blocks (like ignore-blocks) for certain feature(s), e.g:
Obviously this is a contrived/unimaginative example for illustration-purposes. It probably wouldn't be worth trying to support highly sophisticated permutations (like doing "allow-start" for 2 features, then "allow-stop" for 1 of them, then "allow-start" a 3rd, then "allow-stop" 1st & 3rd...), but at least a version which exactly matches the parameter-list in the start and stop commands would be helpful, or even a more simple/robust/flexible-but-more-verbose solution could take only one parameter (so starting/stopping multiple features would require multiple start comments and multiple stop comments...):
Pinging @akrawitz ("allow" creator) and @cwygoda ("ignore" creator) for feedback. Do you have suggestions for better syntax than I suggested? Also, if someone does implement allow-blocks ("ignore" syntax), for the sake of symmetry is it worth also implementing ignore-lines ("allow" syntax)? (which would be an easy hack).
I think having an common set of ways to specify allow and ignore on line and block level would be good. This could also be used to implement both features in a common way to reduce complexity.
With great joy I saw the csslint-ignore-block and csslint-allow-line features were merged recently (I've been cherrypicking them both for personal use since they were PR-ed). It would be nice if we could also have multiline allow-blocks (like ignore-blocks) for certain feature(s), e.g:
Obviously this is a contrived/unimaginative example for illustration-purposes. It probably wouldn't be worth trying to support highly sophisticated permutations (like doing "allow-start" for 2 features, then "allow-stop" for 1 of them, then "allow-start" a 3rd, then "allow-stop" 1st & 3rd...), but at least a version which exactly matches the parameter-list in the start and stop commands would be helpful, or even a more simple/robust/flexible-but-more-verbose solution could take only one parameter (so starting/stopping multiple features would require multiple start comments and multiple stop comments...):
However the implementation, the two benefits would be:
The problem when generating from Sass with the existing "allow" oneline-construct can be seen below:
SCSS
...becomes...
CSS
SCSS
...becomes...
CSS
SCSS
...becomes...
CSS
Pinging @akrawitz ("allow" creator) and @cwygoda ("ignore" creator) for feedback. Do you have suggestions for better syntax than I suggested? Also, if someone does implement allow-blocks ("ignore" syntax), for the sake of symmetry is it worth also implementing ignore-lines ("allow" syntax)? (which would be an easy hack).