[plug-in] Ship VS Code's default extensions

[svenefftinge]

VS Code comes with a couple of extensions preinstalled that are expected to exist by other VS Code extensions. So in order to make arbitrary VS Code we need to meet these expectations.

The simplest solution would be to ship with the default vscode extensions. AFAIK they are not on the marketplace, though.

[akosyakov]

Would it be fine if I look at it?

// cc @svenefftinge @benoitf

[akosyakov]

Here is a list of all built-in extension for VS Code 1.30.1. Tested extensions are marked.

• bat
  • [plugin] vs code extensions without main file are ignored #3973
  • [plugin] load VS Code extensions from sources #3976
  • [plugin] snippets contribution are not supported #3972
• clojure
• coffeescript
• configuration-editing
  • [plugin] jsonValidation contribution support #3983
• cpp
• csharp
• css
• css-language-features - we already have it via Monaco, see css/html monaco contributions vs VS Code extensions #3985
• debug-auto-launch
  • [plugin] contributed configurations are not available via content assist #3991
  • [plugin] status bar message cannot be loaded from nls #3992
  • [plug-in] Implement inspect configuration #2289
  • [plugin] race conditions because of late command registration #3994
  • [plugin] window.terminals & window.activeTerminal API support #4024
  • [plugin/status-bar] root ERROR Warning: Encountered two children with the same key #4032
  • command arguments sent from one plugin to another gets wrapped into array #4033
• docker
• emmet
  • Isolate loading and deployment of plugins #3965
  • [plugin] support VS Code built-in menu items #4004 (commandPalette)
  • [plugin] control command enablement based on menus.commandPalette contribution point #4077
  • support VS Code when closure contexts #3986 (menus)
  • implement vscode.executeDocumentSymbolProvider command for emmet VS Code extension #4048
• extension-editing - provide editing support for VS Code extension development, not important for the first stage
• fsharp
• git [plug-in] VS Code Git extensions #4266
  • support vscode scm api #4103
  • support scm menu contributions #4171
• go
• groovy
  • snippets proposed bogusly sometimes #4208
• grunt - excluded, since tasks support far from be completed in Theia
  • support vscode task contribution points #4211
  • tasks contributed by VS Code extensions don't work #4216
• gulp - excluded, since tasks support far from be completed in Theia
  • support vscode task contribution points #4211
  • tasks contributed by VS Code extensions don't work #4216
• handlebars
• hlsl
• html
• html-language-features - we already have it via Monaco, see css/html monaco contributions vs VS Code extensions #3985
• ini
• jake - excluded, since tasks support far from be completed in Theia
  • support vscode task contribution points #4211
  • tasks contributed by VS Code extensions don't work #4216
• java
• javascript
  • [plugin] jsonValidation contribution support #3983
• json
  • [plugin] jsonValidation contribution support #3983
• json-language-features
  • remove dependencies to @theia/json in order to support VS Code JSON language features extensions #4217
• less
  • support vscode task contribution points #4211 (problemMatcher)
• log
• lua
• make
• markdown-basics
• markdown-language-features
  • Add the needed methods for Webview API #3896
• merge-conflict
  • support scm menu contributions #4171
• ms-vscode.node-debug
  • support VS Code when closure contexts #3986 (keybindings)
  • [plugin] support VS Code built-in menu items #4004 (debug/callstack/context)
  • [vscode] handle keybindings in upper-case  #4175
  • active debug session is not properly updated #4176
  • [vscode] support os specific keybindings #4203
  • support debug vs code commands #4204
• ms-vscode.node-debug2
• ms-vscode.references-view
• npm
• objective-c
• perl
• php
• php-language-features
• powershell
• pug
• python
• r
• razor
• ruby
• rust
• scss
  • support vscode task contribution points #4211 (problemMatcher)
• shaderlab
• shellscript
• sql
• swift
• theme-abyss
• theme-defaults
• theme-kimbie-dark
• theme-monokai
• theme-monokai-dimmed
• theme-quietlight
• theme-red
• theme-seti
• theme-solarized-dark
• theme-solarized-light
• theme-tomorrow-night-blue
• typescript-basics
• typescript-language-features
  • support vscode task contribution points #4211 (problemMatcher)
  • implement vscode env API #4446 (env.language)
• vb
• xml
• yaml

TODO:

• activation events ([vscode] support activation events #4199)

[akosyakov]

Closing it since we have a way to consume built-in extensions by now and most of API and contribution points to support them are implemented. Please open individual issues if some incompatibilities arise.