Better labeling for issues / list of high pri tasks?

[JoshuaKGoldberg]

@angelozerr / @egamma I'm very motivated to get this thing to a usable state. How can I as a prospective contributor help out? Is there a list of good first issue issues?

If you could label issues as good first issue / high priority / bug / blocked / etc., that'd be very helpful! 😊

[egamma]

@JoshuaKGoldberg the current implementation of the tslint-language-service is based on code from the vscode-tslint extension. Unfortunately the two code streams have evolved independently and this is now difficult to maintain. We have therefore decided to start fresh and have some initial code that we will publish soon. Looking forward to your contributions in the fresh code base.

//CC @mjbvz

[csvn]

I’m very interested in this new project @egamma. Where can we find out when it’s made public? Will you notify in this repo?

[egamma]

@csvn we will definitely notify this repo when the new repository becomes public // CC @mjbvz

[JoshuaKGoldberg]

@egamma / @mjbvz do you have a rough ball park of time frame? As in, weeks or months?

Context: the lack of typed rule support is a real pain with TSLint + VS Code. If it's months before you're planning on releasing, it'd be more efficient for us to work off of this repository / a fork of it in the meantime to get the very basic features than to wait.

[mjbvz]

We're aiming to get a preview release out this month

[mjbvz]

Here's the repo with the forked plugin: https://github.com/Microsoft/typescript-tslint-plugin

And the vscode extension that contributes this plugin: https://github.com/Microsoft/vscode-typescript-tslint-plugin The extension should be published to the marketplace sometime this week

[lumaxis]

Fantastic news, thanks @mjbvz!

[JoshuaKGoldberg]

Hooray!