7 ms·

I've encountered this situation in multiple projects where style lint was enabled, with only the defaults, and passed the linter without issue. Tailwind is see

I've encountered this situation in multiple projects where style lint was enabled, with only the defaults, and passed the linter without issue. Tailwind is seeing steadily increasingly popularity (and the accompanying backlash) because it is straight forward and does not require something like stylelint to keep you from hurting yourself.

emmacharp 3y ago
Well, that is not using Stylelint I'd say. Within half a day of configuring, you can prevent almost all of the problems denounced in this thread. Ultimately, it really is "a couple hours of thinking/configuring a linter vs. multiple layers of abstraction, complexity and dependencies added to the codebase." Maybe I'm missing something (and be my guest if I do!) but there is an objectively better choice here.
- marcosdumay 3y ago
  Well, that means stylelint has a problem. They should be talking about how to solve it, because nobody wants to not enable debuging information on a develoepr build. If the devs do not acknowledge this as a problem, this means stylelint is a bad piece of software. I really dislike sass the way it's normally used. It was once a necessary hack, but it's mostly not useful anymore. Something that just concatenates your CSS @include on deployment would bring more value nowadays.
  - emmacharp 3y ago
    I'm not sure what you mean about "Stylelint having a problem". There's a default config, with only base rules, without the more opinionated ones. Then you configure/extend it as you would with almost any other tool. Isn't it the way most tools of this kind work? Or am I missing something?
    - marcosdumay 3y ago
      Linters default rules define almost completely how they will be used. It doesn't matter if you think this is reasonable or not. IMO, missing some rules is better than what most tools of this kind do, but something as plain and obvious as "did you enable debugging symbols on the development build?" should be there. And most people will blame the tool if it's missing.
      - emmacharp 3y ago
        Sorry if I'm being obtuse but I still don't understand. As I see it, the problem was one of SASS code architecture. What do you mean then by "enable debugging symbols"? How does that solve the "chaotic file architecture" problem?

emmacharp 3y ago

Well, that is not using Stylelint I'd say. Within half a day of configuring, you can prevent almost all of the problems denounced in this thread. Ultimately, it really is "a couple hours of thinking/configuring a linter vs. multiple layers of abstraction, complexity and dependencies added to the codebase." Maybe I'm missing something (and be my guest if I do!) but there is an objectively better choice here.

marcosdumay 3y ago
Well, that means stylelint has a problem. They should be talking about how to solve it, because nobody wants to not enable debuging information on a develoepr build. If the devs do not acknowledge this as a problem, this means stylelint is a bad piece of software. I really dislike sass the way it's normally used. It was once a necessary hack, but it's mostly not useful anymore. Something that just concatenates your CSS @include on deployment would bring more value nowadays.
- emmacharp 3y ago
  I'm not sure what you mean about "Stylelint having a problem". There's a default config, with only base rules, without the more opinionated ones. Then you configure/extend it as you would with almost any other tool. Isn't it the way most tools of this kind work? Or am I missing something?
  - marcosdumay 3y ago
    Linters default rules define almost completely how they will be used. It doesn't matter if you think this is reasonable or not. IMO, missing some rules is better than what most tools of this kind do, but something as plain and obvious as "did you enable debugging symbols on the development build?" should be there. And most people will blame the tool if it's missing.
    - emmacharp 3y ago
      Sorry if I'm being obtuse but I still don't understand. As I see it, the problem was one of SASS code architecture. What do you mean then by "enable debugging symbols"? How does that solve the "chaotic file architecture" problem?