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

Upcoming linter changes #15

Closed
AsaAyers opened this issue Jun 2, 2015 · 12 comments
Closed

Upcoming linter changes #15

AsaAyers opened this issue Jun 2, 2015 · 12 comments
Labels

Comments

@AsaAyers
Copy link
Member

AsaAyers commented Jun 2, 2015

We're in the process of replacing linter with a rewrite. Our central issue for tracking the plan is https://github.com/AtomLinter/linter-plus/issues/29. We're working hard to make this a smooth transition for you and for your users.

Please let us know here if you'd prefer to do the work yourself. If you have any questions or concerns please join us in our room on gitter.

@Arcanemagus
Copy link
Member

@park9140 @kevinsawicki Do either of you want to update this linter to the new API? I can take a stab at it if instead if you would like, but I don't actually use this linter myself.

@kevinsawicki
Copy link
Member

Do either of you want to update this linter to the new API?

I don't use this linter myself either, I previously just upgraded it to the Atom 1.0 APIs so it wouldn't break.

@Arcanemagus
Copy link
Member

Ah, just tagged the last two people I saw committing/merging stuff 😉.

@Arcanemagus
Copy link
Member

I'll dig into this tomorrow if @park9140 hasn't responded by then, don't want people stuck on linter@1.2.4 forever just because their favorite linter hasn't been updated.

@park9140
Copy link
Member

@Arcanemagus, I don't have time to work on this today or tomorrow. I will probably get annoyed by it being broken by the end of the week though if you don't have time for it.

@tomitrescak
Copy link

If you would update those API calls, would be very much appreciated! Can't really use new typescript because of this. Thanks!

@markvandenbrink
Copy link

👍 Would be great if the TypeScript linter starts working again. Thanks for all the hard work!

@markvandenbrink
Copy link

Any news on the required changes to fix tslint? Is a complete rewrite necessary? I really miss the TypeScript linter in Atom :-( Let me know if any help is appreciated, though I am not yet familiar with the linter API. I'm curious about the required work...

@Arcanemagus
Copy link
Member

@markvandenbrink essentially this does involve a re-write. You can create a wrapper around the old way of doing things, but often it's just as simple to write it from scratch. I haven't had time to deal with this so I'm sure @park9140 (and everyone using this) would love it if you would take a stab at it 😉.

I would recommend taking a look at how some of the other linters work and just emulating that.

@tomitrescak
Copy link

Hello, I know that this is open-source project which you guys most probably do in your spare time (I have several of my own), but leaving, 13.000 people hanging like this is not cool :/ If it would be an enhancement I can completely understand, but maintenance ... It's been a month now since this package is out of order. Is it really that difficult to remap to new API with your previous experience with linter?

@AsaAyers
Copy link
Member Author

AsaAyers commented Sep 2, 2015

I don't write code for projects I don't use. It has been 70 days since 1.0
launched, someone who depends on this linter can step up and maintain it.

I'm not aware of any other linter with this problem. They have all either
been updated or even the users have abandoned them.
On Sep 1, 2015 8:02 PM, "Tomas Trescak" notifications@github.com wrote:

Hello, I know that this is open-source project which you guys most
probably do in your spare time (I have several of my own), but leaving,
13.000 people hanging like this is not cool :/ If it would be an
enhancement I can completely understand, but maintenance ... It's been a
month now since this package is out of order. Is it really that difficult
to remap to new API with your previous experience with linter?


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

@park9140
Copy link
Member

park9140 commented Sep 2, 2015

I threw together a fix. Report issues on #21 if they seem related otherwise create new issues.

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

No branches or pull requests

6 participants