Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

Linters needing a rewrite #9

Open
18 of 22 tasks
Arcanemagus opened this issue Dec 12, 2015 · 10 comments
Open
18 of 22 tasks

Linters needing a rewrite #9

Arcanemagus opened this issue Dec 12, 2015 · 10 comments

Comments

@Arcanemagus
Copy link
Member

Arcanemagus commented Dec 12, 2015

The following linters implement the linter 0.X API and need a rewrite:

The following linters were never implemented:

The following repos have been deleted:

The following repos have been deleted, but implemented elsewhere by a third-party:

The following linters have been delisted and archived:

And these have been rewritten 🎉:

@Arcanemagus
Copy link
Member Author

Turns out linter-haml just looks like the old style, it's actually working currently.

@Arcanemagus
Copy link
Member Author

Looks like I missed linter-erb.

@Arcanemagus Arcanemagus reopened this Dec 28, 2015
@Arcanemagus
Copy link
Member Author

linter-erb re-written, everything should be updated now! 🎉

@Arcanemagus
Copy link
Member Author

Missed linter-erlc somehow...

@Arcanemagus Arcanemagus reopened this Jan 14, 2016
@Arcanemagus
Copy link
Member Author

I'm not sure how I generated that list before, but it seriously needs review, going over all the repos looking for this now.

@Arcanemagus
Copy link
Member Author

Added 20 linters to the list 😭.

@AsaAyers
Copy link
Member

Correct me if I'm wrong, but linter dropped support for these months ago. So anything that hasn't been updated must not have many users. What is the goal here? To draw attention to unused linters and rewrite them?

@Arcanemagus
Copy link
Member Author

The goal initially is to just document which linters are currently guaranteed to be unusable so they can be evaluated. Some should probably just be completely removed like linter-jsxhint, since it's linter has been deprecated.

You are completely right that if nobody has stepped up to update them so far the user base is probably small. It could be that none of the potential users feel comfortable enough with writing an Atom package to undertake re-writing the linter to work with the new API.

At the worst case, it's a list of something to do when I get bored, which might help somebody who couldn't do it on their own.

@AsaAyers
Copy link
Member

I think there were about 178 repositories when I opened all the issues about linter being rewritten. I'm very glad you're taking the initiative to try to get some of that cleaned up. Thanks :)

@Arcanemagus
Copy link
Member Author

Yea, would be nice to see the tracking issue, but the link is a 404 now. Trying to see if it can be hunted down as that would be a nice reference.

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

No branches or pull requests

2 participants