microsoft / microsoft/TypeScript
Closing TS 6.0 LS issues
まだ誰も着手していません。
- 主要言語
- Go
- スター
- 111k
- フォーク
- 14.3k
- 平均マージ
- 2日 4時間
- マージ済み PR(30日)
- 132
説明
Acknowledgement
- I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.
Comment
As discussed in our December blog post, we're in the process of closing all bugs related to the JavaScript implementation (AKA Strada AKA TypeScript versions 1.1 through 6.0) of the language service.
Why?
A very large part of the language service has basically been rewritten from scratch:
- We now use LSP instead of a custom protocol
- A large amount of logic was not directly portable, so got hand-authored instead, thus likely has a different set of problems
It's extremely time-consuming (and low-yield) to try to verify these issues, so instead we're taking a more blunt approach and instead doing a one-time bulk close of these issues.
In a future step, we'll also be applying this to PRs that change language service behavior, as all future development efforts should be invested in the native codebase. It's important that 6.0 remain a stable release and merging these PRs would potentially introduce servicing costs that would be better spent on the 7.0 codebase.
Why not tsc bugs too?
The port of the core checker logic is extremely faithful to the existing codebase, so almost every checking bug in TS is still present in the Go version (for better or worse!). We're trying to apply some more aggressive auto-verification of old bugs just to keep things tidy, but auto-closing checker bugs right now would discard too many valid issues.
When?
Now-ish, subject to GitHub API rate limits 🙂
What (should you do about it)?
Please try out your scenario in the TypeScript Native Nightly extension.
Three cases to consider:
- The feature isn't implemented yet, wait and try again later
- If the bug is fixed, no action is needed
- If the bug is still present, please log a new issue in the native repo so we can investigate
Happy coding!
コントリビューションガイド
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
調査の方向性
この issue は実装タスクではなく、一括クローズのお知らせです。TypeScript Native Nightly 拡張機能でシナリオを試してください。機能が実装されていない場合は、待ってから再試行し、バグが残る場合は、VS Code エディターの issue テンプレートを使用して TypeScript Native リポジトリに新しい issue を登録してください。
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- go, typescript
- 領域
- tooling
- issue の種類
- ドキュメント
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 活発さ
- 停滞
- 明瞭さ
- 説明が足りない
- 初心者へのやさしさ
- 1/100