Not Validating

[jgable]

Not Validating

[davidparsson]

The rule ids disallows IDs in selectors, not IDs in general: https://github.com/CSSLint/csslint/wiki/disallow-ids-in-selectors

Dose that explain this? If not, please clarify.

See Rule Details where it gives examples of warnings, using just an ID should throw a warning.

https://github.com/CSSLint/csslint/wiki/disallow-ids-in-selectors#rule-details

[davidparsson]

Yes, right. I don't think this plugin currently supports warnings at all. @jgable, please confirm.

If you want that feature, please create a new issue stating this more clearly. I'd be happy to merge a pull request implementing that.

What's wrong with this issue lol. Process for the sake of process? And
there might be other properties also not working.

On Thursday, 3 March 2016, David Pärsson [email protected] wrote:

Yes, right. I don't think this plugin currently supports warnings at all.
@jgable https://github.com/jgable, please confirm.

If you want that feature, please create a new issue stating this more
clearly. I'd be happy to merge a pull request implementing that.

—
Reply to this email directly or view it on GitHub
#89 (comment)
.

[davidparsson]

For the sake of clarity, so that the first post clearly describes the
actual issue.

tors 3 mars 2016 kl 13:24 skrev James Wilkinson [email protected]:

What's wrong with this issue lol. Process for the sake of process? And
there might be other properties also not working.

On Thursday, 3 March 2016, David Pärsson [email protected] wrote:

Yes, right. I don't think this plugin currently supports warnings at all.
@jgable https://github.com/jgable, please confirm.

If you want that feature, please create a new issue stating this more
clearly. I'd be happy to merge a pull request implementing that.

—
Reply to this email directly or view it on GitHub
<
https://github.com/jgable/grunt-lesslint/issues/89#issuecomment-191705771>
.

—
Reply to this email directly or view it on GitHub
#89 (comment)
.

That's merely process for the sake of process you've identified what the
issue I am facing is after I came to you with a problem.

You don't go back to a client when they tell you somethings broken to tell
them to send you a new ticket. You can make one on your own if you so need
it or you could fix the issue as discovered in this issue.

Cheers

On Thursday, 3 March 2016, David Pärsson [email protected] wrote:

For the sake of clarity, so that the first post clearly describes the
actual issue.

tors 3 mars 2016 kl 13:24 skrev James Wilkinson <[email protected]
javascript:_e(%7B%7D,'cvml','[email protected]');>:

What's wrong with this issue lol. Process for the sake of process? And
there might be other properties also not working.

On Thursday, 3 March 2016, David Pärsson <[email protected]
javascript:_e(%7B%7D,'cvml','[email protected]');> wrote:

Yes, right. I don't think this plugin currently supports warnings at
all.
@jgable https://github.com/jgable, please confirm.

If you want that feature, please create a new issue stating this more
clearly. I'd be happy to merge a pull request implementing that.

—
Reply to this email directly or view it on GitHub
<

https://github.com/jgable/grunt-lesslint/issues/89#issuecomment-191705771>

.

—
Reply to this email directly or view it on GitHub
<
https://github.com/jgable/grunt-lesslint/issues/89#issuecomment-191734120>
.

—
Reply to this email directly or view it on GitHub
#89 (comment)
.

[davidparsson]

I'm actually quite offended by your response. There's no process, I just try to make this as easy as possible for anyone who might be interested in fixing this issue. I do this in my spare time and I have no personal interest in getting this feature implemented. Finally, as long as you're making requests without offering me your money or your time, you're not my client.

A problem was presented for someone to solve. You found the root cause and
refused to fix it.

Congratulations on contributing to the demise of your pet project. We will
take your code out of our application.

On Thursday, 3 March 2016, David Pärsson [email protected] wrote:

I'm actually quite offended by your response. There's no process, I just
try to make this as easy as possible for anyone who might be interested in
fixing this issue. I do this in my spare time and I have no personal
interest in getting this feature implemented. Finally, as long as you're
making requests without offering me your money or your time, you're not my
client.

—
Reply to this email directly or view it on GitHub
#89 (comment)
.

[davidparsson]

I have created #90. I hope that issue describes the use case you're looking for.

Appreciated.

On Thursday, 3 March 2016, David Pärsson [email protected] wrote:

I have created #90 #90.
I hope that issue describes the use case you're looking fore.

—
Reply to this email directly or view it on GitHub
#89 (comment)
.

[jgable]

I was going to say something, but it's just not worth it. The @jwilkinson's of the world are killing the open source community. Thinks I'm a client, has never paid me money for the software I write, or even sent me a birthday card.

Has made no significant contribution to any open source project that I can see. Makes money making websites for credit report companies off my software, then comes and has an attitude about process when we are trying to clarify the issue.

I can't even... I just, can't even.

[davidparsson]

Thanks for your comment, @jgable. It actually means a lot. This single conversation made me so upset yesterday that I seriously considered stopping being an active member of the open source community, because it's just not worth taking shit like this. But I've decided to stay.

And by the way, @jwilkinson. This is much more of @jgable's "pet project" than mine. I'm just some random guy on the internet who thought that grunt-lesslint lacked a few features and decided to help out. Can you imagine that?

[davidparsson]

#90 is implemented and released in v3.1.0