- 04 4月, 2019 1 次提交
-
-
由 Matt Bierner 提交于
-
- 15 2月, 2019 2 次提交
-
-
由 Matt Bierner 提交于
-
由 Matt Bierner 提交于
-
- 29 1月, 2019 1 次提交
-
-
由 Matt Bierner 提交于
-
- 12 1月, 2019 6 次提交
-
-
由 Matt Bierner 提交于
-
由 Matt Bierner 提交于
-
由 Matt Bierner 提交于
-
由 Matt Bierner 提交于
Fixes #66368
-
由 Matt Bierner 提交于
Fixes #66366 Fixes #66367 Avoid printing the error twice in the trace Make sure we show helpful error information in the VS Code dev tools when a TS server error occurrs
-
由 Matt Bierner 提交于
-
- 14 12月, 2018 1 次提交
-
-
由 Matt Bierner 提交于
Fixes #65031 Adds a `enableForWorkspaceTypeScriptVersions` flag (default false) to the plugins contributions that allows a contributed plugin to be loaded for workspace versions of ts
-
- 16 11月, 2018 1 次提交
-
-
由 Matt Bierner 提交于
-
- 15 11月, 2018 3 次提交
-
-
由 Matt Bierner 提交于
-
由 Matt Bierner 提交于
-
由 Matt Bierner 提交于
-
- 27 10月, 2018 5 次提交
-
-
由 Matt Bierner 提交于
Allow for finer control over how requests are queued
-
由 Matt Bierner 提交于
-
由 Matt Bierner 提交于
-
由 Matt Bierner 提交于
-
由 Matt Bierner 提交于
-
- 18 10月, 2018 1 次提交
-
-
由 Karthikayan 提交于
* include priority in requestItem and add to queue accordingly * add boolean lowPriority flag to requestItem and add to queue based on that * set lowPriority flag to optional * send lowPriority flag from CodeLensProvider * revert priorityFlag for provider
-
- 21 9月, 2018 1 次提交
-
-
由 Matt Bierner 提交于
**Problem** In the ts server communication, canceling a request currently throws an exception. This is wrong because cancellation is not an error. It also means that we need to wrap every server call in a generic try catch to handle cancellation. There are no checks in place to distinquish a cancellation from a rea
-
- 20 9月, 2018 1 次提交
-
-
由 Matt Bierner 提交于
-
- 18 9月, 2018 1 次提交
-
-
由 Matt Bierner 提交于
Fixes #58560 If the queued (but not sent) ts server request is canceled, we could previously fail to resolve its callbacks. This change makes sure we always resolve the callbacks for cancelled requests
-
- 14 9月, 2018 1 次提交
-
-
由 Matt Bierner 提交于
Rebase of a number of incremental changes listed below Move first level dispatchMessage into ForkedTsServerProcess Goal is to move callbacks and other per-server state into `ForkedTsServerProcess` Create forked ts server object syncrounously There is no reason for this to be async anymore. Making this object sync reduces complexity and makes the code easier to reason about Moving server relate functions into ForkedTSServer object The goal here is to have a single "server" object that keeps track of all its relevant state. The service client would manage one of these servers at a time, starting new ones if needed and dispatching to old ones Split server into own file Use switch case instead of conditionals Make pendingResponses readonly Add typings for callback item Improve naming - Use more descriptive names - Preview private vars with _ Use passed in version for getting command line args Attach webview click handler to window instead of to document body Fixes #48926 Change error handling for ts server exit and error - Don't fire twice on error (once for the `once` and once for the `onError`) - Flush callbacks on both exit and error. Remove cancellationPipeName as state Remove obsolete comment Move all env generation into generatePatchedEnv Extract server spawn into static method Move spawn from static to be own factory class Move providers from arguments to state on the spawner Update js/ts grammar Remove duplicate error handler Cleaning up server fork - Standarize names - Extract methods - Move some function to be private statics - Move logging out of electron and into server.ts Use undefined instead of null for optional value
-