Skip to content
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

Switch to stylelint. #23383

Closed
bardiharborow opened this issue Aug 13, 2017 · 14 comments
Closed

Switch to stylelint. #23383

bardiharborow opened this issue Aug 13, 2017 · 14 comments
Assignees

Comments

@bardiharborow
Copy link
Member

No description provided.

@XhmikosR
Copy link
Member

XhmikosR commented Aug 13, 2017

Yup, agreed. Note for us, we could/should make use of more postcss plugins.

I'm gonna work on this later today or tomorrow and make a PR to discuss/extend my patch.

@mdo: before I spent more time with this, do you agree with the switch?

@XhmikosR XhmikosR self-assigned this Aug 13, 2017
@mdo
Copy link
Member

mdo commented Aug 13, 2017

do you agree with the switch?

Have we discussed it at all? What's the benefit? I know we had #20402, but I don't completely remember why there was a repo for it and why our linting rules had so many changes.

@XhmikosR
Copy link
Member

XhmikosR commented Aug 13, 2017 via email

@mdo
Copy link
Member

mdo commented Aug 13, 2017

if there's a config we have control of

We don't have that. It was suggested, but I don't know what it included or why that was suggested.

@XhmikosR
Copy link
Member

XhmikosR commented Aug 13, 2017 via email

@mdo
Copy link
Member

mdo commented Aug 13, 2017

I can make a config which results in no code changes and then we can make it stricter. How does that sound?

Still doesn't answer why we'd switch—what's the difference between the two?

@XhmikosR
Copy link
Member

XhmikosR commented Aug 13, 2017 via email

@FezVrasta
Copy link
Contributor

Probably a long term decision to move away from Sass in future?

@mdo
Copy link
Member

mdo commented Aug 19, 2017

Stylelint is very extendable and no Ruby requirement.

Ayyy that's all you have to say to me :D.

@mdo
Copy link
Member

mdo commented Aug 19, 2017

Probably a long term decision to move away from Sass in future?

Yeah eventually :)

@XhmikosR
Copy link
Member

Cool, I'll make a PR and CC you with the minimum rules so that we extend it match our needs before merging.

@bardiharborow
Copy link
Member Author

Still doesn't answer why we'd switch—what's the difference between the two?

Do I need to say much more that this pretty screenshot? 😍

The main thing is that Ruby Sass, and by extension scss-lint is being gently depreciated, so stylelint is the clear migration path, in addition to being more architecturally similar to our use of ESLint for JavaScript.

@XhmikosR
Copy link
Member

I'm gonna push my branch when I have some time to clean it up and CC you guys so that we bring the rules on par or even better with scss-lint.

@XhmikosR XhmikosR mentioned this issue Aug 20, 2017
4 tasks
@rafalp
Copy link

rafalp commented Sep 10, 2017

I would like to add my vote for this move. Ideally building css/js in Bootstrap should require npm install. I can bite the bower as its node.js too, but if my app's in python, it'll be worked with by python devs, why the heck do I need to install ruby things? ;)

@mdo mdo closed this as completed in #23572 Oct 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants