* initial language detection
* add configuration and extra event on UntitedTextEditorService
* check isWeb, use beter mode API, include model in unpacked
* typo in path
Fixes: https://github.com/microsoft/vscode/issues/115101.
See issue for details.
- Adopts the new API
- Test results now persist across reloads (last 64 runs).
- Removed state grouping in favor of sorting option.
- Code lenses are disabled for now
* move encoding.ts to common for #79275
* load iconv-lite-umd and jschardet in web version for #79275
* move EncodingOracle to the AbstractTextFileService for #79275
* review
* update to new iconv-lite-umd
* add workaround for jschardet types
* fix indentation
* add iconv-lite-umd and jschardet to workbench.html
* fix paths for modules
Co-authored-by: Benjamin Pasero <benjpas@microsoft.com>
For #77131
**Motivation**
While our existing webview editor API proposal more or less works, building an editable webview editor is fairly tricky using it! This is especially true for simple text based editors.
It'd also be nice if we could get bi-directional live editing for text files. For example, if I open the same file in a webview editor and in VS Code's normal editor, edits on either side should be reflected in the other. While this can sort of be implemented using the existing API, it has some big limitations
**Overview of changes**
To address these problems, we've decided have two types of webview editors:
- Text based webview editors. These editors used a `TextDocument` as their data model, which considerably simplifies implementing an editable webview. In almost all cases, this should be what you use for text files
- Complex webview editors. This is basically the existing proposed API. This gives extension hooks into all the VS Code events, such as `save`, `undo`, and so on. These should be used for binary files or in very complex text editor cases.
Both editor types now have an explicit model layer based on documents. Text editor use `TextDocument` for this, while custom editors use `WebviewEditorCustomDocument`. This replaces the delegate based approach previously used.
