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

shared stylelint-config-airbnb #56

Closed
wants to merge 24 commits into from
Closed

shared stylelint-config-airbnb #56

wants to merge 24 commits into from

Conversation

christophervoigt
Copy link

To be fair, most of this comes from #23 and serves #13, but instead of having to merge with @ntwb (:+1:) each time, I wanted to create my own for faster development.

So what's new?

  • I mostly rewrote the package following the example of the current airbnb/javascript repository.
  • I also added some basic tests to the package.

Please feel free to comment or suggest improvements.

Copy link

@ntwb ntwb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ntwb
Copy link

ntwb commented Nov 4, 2017

Great idea @chlorophyllkid, a quick cursory glance at everything looks 👌

I've now closed #56 🎉

@felixjung
Copy link

Neat, looking forward to this.

@christophervoigt
Copy link
Author

I had to remove the rule 'scss/dollar-variable-pattern': '^foo' because having to start every variable with foo seems a bit odd. 😉
If it should be part of the ruleset again, a proper regular expression should be created to fit the naming conventions.

'^[_a-z][\\w-]*$' should fit the naming conventions
'number-leading-zero': 'never',
'scss/double-slash-comment-inline': 'never',
'order/order': ['declarations', 'at-rules', 'rules'],
removed 'no-invalid-double-slash-comments': true,
changed 'at-rule-empty-line-before': ['always', { except: ['first-nested'] }]
@christophervoigt
Copy link
Author

christophervoigt commented Nov 18, 2017

Ok, I did a bunch of things today. Let me conclude:

I added the scss-lint file again, which I removed during the restructuring.
It took me a while to understand some of those rules, but in the end I added some new rules to the index.js of the new package, which now should hold every rule / recommendation of the current README and scss-lint. (please review) 😉

Tests are now in different files as well. The base-files are mostly for formatting rules and the sass-files are more specific to scss syntax.

@felixjung
Copy link

Hey there. Can we get any response from the maintainers on this? Would be great to get this going. 😃

@tony
Copy link

tony commented Jan 1, 2018

I'm excited about this. The tricky issue is airbnb apparently doesn't do stylelint in-house (#45), so I'm concerned that may cause friction with getting this in. They don't really have a way to maintain a shareable config if they don't use the linter.

So getting a yes/no response if airbnb is willing to officially support a stylelint config would be helpful. If the answer is no, it may be best to press forward with a separate repo. Aside: we could ask if stylelint organization would help, but the bigger picture is we need volunteers using stylelint that can help maintain it.

Doing some QA:

Was wondering the markdown lint stuff for. It's based off https://github.com/airbnb/javascript/tree/master/linters.

For reference, there is the layout of stylelint "shareable configs", which is pretty similar in spirit to what eslint offers:

To try to get some more eyes on this, I'm posting an issue in stylelint/stylelint. stylelint/stylelint#3091

@ntwb
Copy link

ntwb commented Jan 2, 2018

So getting a yes/no response if airbnb is willing to officially support a stylelint config would be helpful.

Accepting a PR for this was green-lighted in #13 (comment)

Aside: we could ask if stylelint organization would help

I am one of the members of the stylelint org and created the original PR for this 😏

To try to get some more eyes on this, I'm posting an issue in stylelint/stylelint. stylelint/stylelint#3091

I've replied and closed that issue 😄

@tony
Copy link

tony commented Jan 2, 2018

Thanks for responding to stylelint/stylelint#3091

I'm glad to know stylelint is already greenlighted in #13. That will make this process smoother.

@christophervoigt
Copy link
Author

but the bigger picture is we need volunteers using stylelint that can help maintain it.

I would be definitely up for this. :)

@ntwb
Copy link

ntwb commented Jan 2, 2018

I know Airbnb's shared ESlint configuration is popular and all but if all you're are after ia a shared stylelint configuration with some sane defaults to use in your projects then use:
https://github.com/stylelint/stylelint-config-standard

The stylelint-config-standard configuration inherits:
https://github.com/stylelint/stylelint-config-recommended

@christophervoigt
Copy link
Author

christophervoigt commented Jan 2, 2018

I'm familiar with those, and I'm actually using stylelint-config-standard with some rule overrides. That wasn't the point of this PR and working towards this.
Since airbnb already acts for a lot of developers as a source of truth and good practise, I was wondering why this repository isn't an actual stylelint extention yet.

If airbnb decides to not merge those changes, I might end up copying a lot of those rules into my future project rulesets. 😄

@stevenleija
Copy link

Any updates on this?

@SilentImp
Copy link

So, actually, why it's still not merged?
Help needed?

@lencioni
Copy link
Contributor

Thanks for the contribution! At a glance this looks pretty good to me. @ljharb can you review this when you have a chance?

@alisonps
Copy link

Hi! Are there any updates on the status of this?

@christophervoigt
Copy link
Author

No, still waiting for the review of @ljharb and @mikefowler 🙂

@kytta
Copy link

kytta commented Dec 31, 2019

...so? It's been 1.5 years. Is there even a point in waiting?

@tianzhich
Copy link

3 years later...😞

@christophervoigt
Copy link
Author

I'm going to close this now ...this is clearly never going to happen. 😄

Thank you everyone for your patience. Stay Safe! 👋

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.