microsoft / microsoft/TypeScript-Sublime-Plugin
Unmaintained and buggy (especially with ST4) + an alternative
まだ誰も着手していません。
- 主要言語
- JavaScript
- スター
- 1.7k
- フォーク
- 236
- 平均マージ
- 21日 13時間
- マージ済み PR(30日)
- 1
説明
This package hasn't been properly maintained for a long time and doesn't look like Microsoft wants to put any resources on it apart from occasionally bumping the typescript dependencies and tweaking the syntax.
The current issues known to me (at least when using ST4) are:
- comes with a Typescript syntax while ST4 has now a built-in syntax that is of much higher quality and should be used instead
- has issue with completions being triggered at wrong times (like after semicolon) (https://github.com/microsoft/TypeScript-Sublime-Plugin/issues/776) (https://github.com/microsoft/TypeScript-Sublime-Plugin/issues/773)
- has issues with synchronizing document state resulting in the diagnostics getting out of sync sometimes and other issues (https://github.com/microsoft/TypeScript-Sublime-Plugin/issues/761)
- does not use utf-16 encoding (API available since ST4) when communicating with the server resulting also in synchronization issues
- overrides built-in keybindings which is a very bad practice (https://github.com/microsoft/TypeScript-Sublime-Plugin/issues/736)
- known performance issues (https://github.com/microsoft/TypeScript-Sublime-Plugin/issues/716) (https://github.com/microsoft/TypeScript-Sublime-Plugin/issues/654) (https://github.com/microsoft/TypeScript-Sublime-Plugin/issues/317)
- Doesn't take advantage of new features introduced in ST4 (improvements to completions handling, ability to do partial document updates) resulting in poor experience and lower performance
Due to providing generally a poor experience for the users, the ST community has decided to restrict availability of this package to ST3 (https://github.com/wbond/package_control_channel/pull/8479) as the quality of this very popular package can heavily influence how people see ST as an editor and think that it is just worse editor than the "competition".
Note that there exists a much better alternative to this package which is the generic https://packagecontrol.io/packages/LSP package in combination with the https://packagecontrol.io/packages/LSP-typescript helper package. It's actively maintained, supports all new functionality of ST4 and is performant so that is the recommended way to go forward.
Assuming that there is not gonna be any effort put into fixing those issues, it would be appreciated if the package also mentioned that it's deprecated for ST4 and maybe suggest the alternative.
コントリビューションガイド
このリポジトリのコントリビューションガイドは索引されていません
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
調査の方向性
この issue にはファイル、テスト、エントリーポイントのいずれも記載されていません。まずパッケージのユーザー向けドキュメントを確認し、その後、ST4 では非推奨であることを文書化して、推奨される代替手段として LSP-typescript を使用した LSP をユーザーに案内してください。基盤となる統合を変更せずに、非推奨の通知と移行方法が明確に表示されれば完了です。
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- typescript
- 領域
- documentation
- issue の種類
- ドキュメント
- 難易度
- 2/5
- 見積もり時間
- 1〜3時間
- 活発さ
- 停滞
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 35/100