microsoft / microsoft/TypeScript-Sublime-Plugin
Unmaintained and buggy (especially with ST4) + an alternative
Personne n'a encore pris cette issue.
- Langage dominant
- JavaScript
- Étoiles
- 1.7k
- Forks
- 236
- Merge moyen
- 21 j 13 h
- PR mergées (30 j)
- 1
Description
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.
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Piste de recherche
L’issue ne mentionne aucun fichier, test ni point d’entrée. Consultez d’abord la documentation du package destinée aux utilisateurs, puis documentez qu’il est obsolète pour ST4 et orientez les utilisateurs vers LSP, avec LSP-typescript comme alternative recommandée. Le travail est terminé lorsque l’avis et le parcours de migration sont clairement visibles sans modifier l’intégration sous-jacente.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- typescript
- Domaine
- documentation
- Type d'issue
- Documentation
- Difficulté
- 2/5
- Temps estimé
- 1-3 heures
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 35/100