Closed tsmaeder closed 4 years ago
Where there is a version number, the API was introduced after the version of the API we initially targeted (1.29.1)
Collected from https://github.com/eclipse/che/issues/12996. I haven't looked at the "dynamicCommandCalls" yet. These might reveal more used commands.
List now includes dynamic command invocations. Note that we can't really track commands that might be originating in language servers (CodeActions, for example), but they should not rely on the host being VS Code, so if they are clean, we are ok.
vscode.java/0.42.0 is also using vscode.extensions.onDidChange() which is not available.
Thanks for detecting that. The bigger question, though: which is that not being picked up by the tool? If it's not reliable, it's a lot less useful.
I'll need to do another pass over the repos, unfortunately. The positives still are real positives that should be fixed.
Reran the checks with the newest version of the tool and master of the extensions
Issues go stale after 180
days of inactivity. lifecycle/stale
issues rot after an additional 7
days of inactivity and eventually close.
Mark the issue as fresh with /remove-lifecycle stale
in a new comment.
If this issue is safe to close now please do so.
Moderators: Add lifecycle/frozen
label to avoid stale mode.
This lists missing VS Code API referenced from Language Support Plugins used in Che 7 GA.