- 23 7月, 2020 1 次提交
-
-
由 Marco Goertz 提交于
Replacing ILanguageServerProtocol with AbstractRequestHandlerProvider. Refactoring common Extensions method code into generic helpers.
-
- 21 7月, 2020 1 次提交
-
-
由 Marco Goertz 提交于
Added XAML LSP shims by introducing ILanguageServerProtocol and adding an optional Language parameter to the ExportLspMethodHandlerAttribute so that XAML can export its own LSP handlers. Added a few extension methods to make dealing with TextDocuments easier.
-
- 13 6月, 2020 1 次提交
-
-
由 Allison Chou 提交于
-
- 12 6月, 2020 1 次提交
-
-
由 N. Taylor Mullen 提交于
- The language server platform is properly implementing solution close understanding for local language servers and I found that when testing their bits Roslyn would explode gloriously. Turns out shutdown and exit support just wasn't fully enabled yet. - When the language server platform reboots language servers it re-invokes Activate and because of that Roslyn explodes because the language client has already been activated and there was previously a contract throws check on already being initialized. - Implemented the `ShutdownAsync` target on the `InProcLanguageServer` to detach from the diagnostic service. - Implemented the `ExitAsync` target on the `InProcLanguageServer` to properly dispose our `JsonRpc` object.
-
- 06 6月, 2020 1 次提交
-
-
由 Allison Chou 提交于
-
- 04 6月, 2020 1 次提交
-
-
由 David Barbet 提交于
-
- 19 5月, 2020 2 次提交
-
-
由 Jason Malinowski 提交于
-
由 Jason Malinowski 提交于
This replaces our existing "GetDocumentFromURI" helper with one that instead takes the full TextDocumentIdentifier, and uses the context information to figure out which document to use in the case of multi-targeting or linked documents.
-
- 16 5月, 2020 1 次提交
-
-
由 Jason Malinowski 提交于
-
- 06 5月, 2020 1 次提交
-
-
由 David Barbet 提交于
-
- 01 5月, 2020 1 次提交
-
-
由 David Barbet 提交于
-
- 21 4月, 2020 1 次提交
-
-
由 David Barbet 提交于
-
- 18 4月, 2020 3 次提交
-
-
由 David Barbet 提交于
-
由 David Barbet 提交于
-
由 David Barbet 提交于
-
- 16 4月, 2020 1 次提交
-
-
由 David Barbet 提交于
-
- 11 4月, 2020 1 次提交
-
-
由 Allison Chou 提交于
-
- 07 4月, 2020 1 次提交
-
-
由 Allison Chou 提交于
-
- 03 4月, 2020 2 次提交
-
-
由 David Barbet 提交于
-
由 David Barbet 提交于
-
- 02 4月, 2020 1 次提交
-
-
由 David Barbet 提交于
-
- 01 4月, 2020 1 次提交
-
-
由 David Barbet 提交于
-
- 31 3月, 2020 2 次提交
-
-
由 Allison Chou 提交于
-
由 David Barbet 提交于
-
- 28 3月, 2020 8 次提交
-
-
由 David Barbet 提交于
Update diagnostics publishing to include uris from previously published diagnostics as well as current diagnostics.
-
由 David Barbet 提交于
-
由 David Barbet 提交于
-
由 Jason Malinowski 提交于
ASP.NET Razor is prototyping a system where they can add files into our workspace via IDynamicFileInfoProvider and can then query our LSP server to get diagnostics about those files. They're normally closed files but we want them to get analyzed always if they want to query them via LSP, and we also don't want those diagnostics to end up in the error list since further processing needs to be done with them with LSP. This implements a hook where Razor can specify that diagnostics produced for their documents are ingored by most of the system, but can still be queried through their special LSP server.
-
由 David Barbet 提交于
-
由 David Barbet 提交于
-
由 David Barbet 提交于
Razor needs us to return the mapped span so that the diagnostics are properly located in the actual razor file, rather than the underlying c# buffer. In non razor scenarios, it appears that the mapped span = original span, so it should be safe to always return the mapped span. The diagnostic data location's SourceSpan doesn't appear to ever be mapped so we ignore it.
-
由 David Barbet 提交于
-
- 27 3月, 2020 1 次提交
-
-
由 Allison Chou 提交于
-
- 12 3月, 2020 1 次提交
-
-
由 David 提交于
-
- 11 3月, 2020 1 次提交
-
-
由 David Barbet 提交于
-
- 04 3月, 2020 1 次提交
-
-
由 Allison Chou 提交于
-
- 25 2月, 2020 1 次提交
-
-
由 David Barbet 提交于
-
- 14 2月, 2020 1 次提交
-
-
由 Allison Chou 提交于
-
- 13 2月, 2020 2 次提交
-
-
由 Allison Chou 提交于
-
由 Allison Chou 提交于
-