Shane da Silva

Thank you for writing up a detailed proposal for this potential feature, @thegranddesign. The `PropertySort` linter is already notoriously complicated. Each new "option" we add to it further complicates things....

Happy to accept a pull request implementing this, @tnir!

I understand where you are coming from, but you really have to ask yourself if using functions/maps is going with the spirit of what the check is intended to enforce....

I see your point, @VincentSmedinga (though to be honest I don't feel strongly either way). Happy to accept a pull request allowing `VariableForProperty` to allow maps. Thanks for your input!

Thanks for the detailed explanation of the issue, @jamieconnolly. Would love to get a pull request that addresses this, as it's a pretty specific issue that would take some time...

Hey @petrgazarov, Code inside comments will only be linted if you are using "loud" comments (`/*...*/`). Since those comments are rendered to the resulting CSS, they support interpolation of Sass...

I'm initially opposed to this because of the complexity involved and my belief that you can't do this properly in the general case. The moment you allow linters to be...

Interesting. So does ESLint actually let you change the configuration part way through the file? Or do these comments only work at the top of the file? My lack of...

Thanks for the report, @rvanlieshout! This problem can be reproduced by splitting an asterisk-prefixed property across multiple lines, e.g.: **Trigger Case** ``` scss .class { width: 100%;* //

Thanks for taking the time to put together some of your ideas, @srawlins. I agree it's not ideal from a performance perspective that we're visiting the same nodes over and...