-
Notifications
You must be signed in to change notification settings - Fork 530
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New rule: space around operator #124
Conversation
}; | ||
|
||
module.exports = { | ||
'name': 'space-around-colon', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be space-around-operator
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bgriffith Good catch. Should be fixed now.
0fbccdc
to
998cd76
Compare
Hey @skovhus thanks for this, we'll leave it on review until 1.2.0 is out. I believe we are planning to move to using a develop branch post 1.2 to enable us to simultaneously release hot fixes to master if necessary while continuing to develop and merge rules and features. As you pointed out too we're awaiting a new release of |
@DanPurdy makes sense. Looking forward to 1.2.0. After that https://github.com/skovhus/SublimeLinter-contrib-sass-lint should be ready for use. : ) Out of curiosity, what were the considerations in choosing |
Yeah it's gonna be good to get 1.2.0 out, and a sublime linter plugin ready to go is also great news! 👍 I've only come on board recently as I'm looking forward to moving away from the ruby dependencies in some of our projects. @Snugug has talked about it in a few of the earlier issues though., but he will be able to tell you why exactly. |
998cd76
to
dcd16ae
Compare
Gonzales was chosen because Libsass (the compiler that Node Sass uses) doesn't provide its AST publicly and, in its current state, wouldn't be useable enough for linting. There is an issue in Libsass to expose the AST, but until that lands (and the AST is robust enough to support writing a linter against), we can't use it for Sass Lint. |
@Snugug Thanks for clarifying. Another thing now that we are talking about the background of this project: what are your vision in terms of rules porting? Do you imagine sass-lint to port all scss-lint rules and their many options? |
If you want to discuss this, please open an issue to discuss roadmap
|
This will need to be re-rolled off of the |
Hey @skovhus this is ready for a new PR to be created in to develop if you have the time. Thanks! |
I'm going to close this for now. I've just run through it to update with sass tests and even a few of the scss tests aren't doing what they are supposed to. Will definitely need more work. |
This resolves #31.
Due to bugs in
gonzales-pe
the following will currently fail:DCO 1.1 Signed-off-by: Kenneth Skovhus [email protected]