Turn stylelint-config-standard into an actual standard

[corysimmons]

It favours flexibility over strictness for things like multi-line lists and single-line rulesets, and tries to avoid potentially divisive rules.

Is fine and all, but it's not a standard.

Flexible != Standard

You should rename this repo to stylelint-config-flexible and create an actual standard.

That's kind of the whole point behind linting anything to enforce strict rules for code quality.

Please take a page out of https://github.com/feross/standard handbook and become the one standard to rule them all.

[corysimmons]

I've thoroughly documented the problems I've had with stylelint in stylelint repo, Atom Linter repo, and Sublime Linter repo, as well as a couple other places.

The problem is you guys don't have official/functional linters for any of the major editors.

A linter without linters is not usable. How the hell did this slip by everyone?

I'm not upset that it's not usable. I'm happy you guys are working on a neat project to test out your JS/PostCSS chops. I'm upset that not one of you has actually used it and it's being marketed as a real world solution.

If I make a grid, I browser test it... I actually use it... I try to break it.. then I release it.. then I get feedback and work on it some more. Finally I make a website for it and market it. You guys made stylelint, skipped all that other stuff and went straight to marketing it.

[MoOx]

Wow.

it's being marketed as a real world solution

Where did you see that?

The problem is you guys don't have official/functional linters for any of the major editors.

Is this serious? Why don't you just do it? You are talking like "we" (note: I am not a maintainer) are supposed to provide everything "you" need. People here have worked really hard and have developed an awesome tools with hundreds of rules like nobody made this before. Just look at other css linters... Oh there is no one that really works these days...

---

Most developers, actually use a terminal to build there project. That's where they see warnings and shit. And if you are more a "GUI" guy, you still have stuff like postcss-browser-reporter.

Saying that people code this and don't use this it just stupid. That's so obvious that "they" use it everyday.

Marketing is bullshit. There is no fucking marketing. They just share their works, that's it. The website is not even a real one (and nobody have said the opposite).

Sorry but you are talking like a dick that is looking to the "ultimate solution that fits all my needs".

There is no such things. Just contribute, like stylelint maintainers did, piece by piece, commit by commit, instead of saying "lol I am done with your unfinished untested work that no one can use".

[corysimmons]

No need to be sorry, I'm not a baby like the rest of GitHub, but if you wanna cuss me out in private I can get on gitter?

"ultimate solution that fits all my needs"

Nah, I just want a linter that can lint in an editor rather than having to check a terminal task after every keystroke.

I would contribute if I were better at JS. I'm learning now, but time I could have spent studying was wasted trying to wrestle this project into basic functionality.

I was contributing in my own way though with a thought-out/strict standard that probably would've made stylelint a bit more popular.

Where did you see that?

I didn't see anything in the impressive feature list on http://stylelint.io or the stylelint README that eluded that it didn't have functional plugins for editors.

Why don't you just do it?

1. It's not my project so I shouldn't have to.
2. I'm not great at JS so I can't.
3. I'm not upset about it being an unfinished project. I'm upset about there not being a disclaimer that it's not usable.

[MoOx]

I was contributing in my own way though with a thought-out/strict standard that probably would've made stylelint a bit more popular.

I said step by step, and here you are directly trying to achieve the final step. I agree that's a must have (I am very happy with eslint in atom) but you can't blame people for not doing something you want or need.

Btw, if you need a linter at every keystroke, maybe there is a problem with your CSS too ;)

[corysimmons]

you can't blame people for not doing something you want or need.

For the 3rd time: I don't care that the tool isn't production ready. I care that there's no disclaimer warning others that stylelint can't be used like a real linter since it doesn't work in any editor.

if you need a linter at every keystroke, maybe there is a problem with your CSS too

I'm trying to introduce a real CSS standard with property sorting (can you remember what order every single css property goes in?) instead of these lax configs you guys are using.

[MoOx]

I care that there's no disclaimer warning others that stylelint can't be used like a real linter since it doesn't work in any editor

Like I said, that's your fault. You have to check this before using a tool. For you information ESLint for example don't have an official atom linter plugin. The plugin is unofficial and had in the past lot's of failures. All those things demand time, and time is nor free or unlimited.

I'm trying to introduce a real CSS standard with property sorting instead of these lax configs you guys are using.

Again, step by step.

[corysimmons]

I did try out the linters first. They seemed to work until you throw a custom config at them.

So in this order:

1. Found stylelint and assumed something called stylelint could lint in a practical manner
2. Got plugins working for it
3. Spent days working on a stylelint config and reporting little bugs as I ran into them
4. Realized I had reported dozens of bugs and that I wouldn't be able to use my config for months

I'm not asking for an apology or anything. I just want you guys to put a disclaimer somewhere semi-prominent on your README and website that editor linting isn't supported and probably won't be for months.

[davidtheclark]

Ok, @corysimmons. Please go away.