- 07 7月, 2020 2 次提交
-
-
由 Johannes Rieken 提交于
-
由 Alex Dima 提交于
-
- 06 7月, 2020 1 次提交
-
-
由 Rachel Macfarlane 提交于
-
- 02 7月, 2020 1 次提交
-
-
由 isidor 提交于
#101429
-
- 29 6月, 2020 1 次提交
-
-
由 João Moreno 提交于
-
- 25 6月, 2020 1 次提交
-
-
由 isidor 提交于
#100852
-
- 24 6月, 2020 2 次提交
-
-
由 Alex Ross 提交于
Part of #100741
-
由 Pascal Fong Kye 提交于
* refactor: use array of resources * refactor: use an array of uricomponentspair * feat: move many resources * refactor: rename data to files * feat: use array of files for copy * refactor: use move with multiple resources * refactor: use move method with array of files * refactor: rename data to files * feat: moveOrCopy array of resources on paste * refactor: use concise loop syntax * test: assert number of events * refactor: rename uricomponentspair * support multiple files on WorkingCopyFileEvent * feat: support multiple resources onWillRunWorkingCopyFIleOperation onDidRunWorkingCopyFileOperation * refactor: make source optional for consistency * refactor: support resources for delete * test: isolate tests * fix: iterate over resources * feat: support operations on delete * feat: adopt deleting multiple resources * fix: typing and sequential flow of copyservice * fix: typing and naming * fix: typing and naming * fix: use different message for multiple overwrites * refactor: naming consistency * fix: use array resources * fix: message for multiple overwrites * fix format * clean up working copy file service * refactor multiple overwrites message helper * use openeditors to bulk open * split drop copy and move * add returns Co-authored-by: NBenjamin Pasero <benjpas@microsoft.com>
-
- 23 6月, 2020 2 次提交
-
-
由 Johannes Rieken 提交于
send requests per provider so that a hanging provider doesn't block other providers, https://github.com/microsoft/vscode/issues/100524
-
由 Connor Peet 提交于
* notebooks: pipe renderer API postmessages to the renderer itself Previously the postMessage on acquireNotebookRenderer API was just a proxy to the global vscode postmessage. Now, it's linked to the renderer and will cause an optional `onDidReceiveMessage` method on the renderer to be called. The message still _also_ goes to the global webview message handling for advanced use cases, but this change allows the webview<->renderer communication to be more nicely contained and separate for most use cases. * wip * fixup! pr comments
-
- 18 6月, 2020 4 次提交
-
-
由 Daniel Imms 提交于
-
由 Alex Dima 提交于
-
由 rebornix 提交于
-
由 Daniel Imms 提交于
-
- 17 6月, 2020 3 次提交
- 13 6月, 2020 3 次提交
-
-
由 rebornix 提交于
-
由 Connor Peet 提交于
Some API changes: - I changed the second param of NotebookOutputRenderer.render to a `NotebookRenderRequest` since we were up to four parameters already. - The request contains a unique `outputId`, which is generated when output is first created or restored (the ID is not stable if a notebook is closed and reopened) - I changed the renderer events to `onDidCreateOutput` and `onWillDestroyOutput` since they're for outputs, not cells. - Additionally, they're called with objects that contain the output ID to render.
-
由 Daniel Imms 提交于
-
- 12 6月, 2020 4 次提交
- 30 5月, 2020 1 次提交
-
-
由 Johannes Rieken 提交于
-
- 29 5月, 2020 1 次提交
-
-
由 Johannes Rieken 提交于
notebooks - wire up onDidChange event from notebook providers, fyi @rebornix, https://github.com/microsoft/vscode/issues/96403
-
- 27 5月, 2020 1 次提交
-
-
由 rebornix 提交于
-
- 20 5月, 2020 2 次提交
-
-
由 Rachel Macfarlane 提交于
-
由 rebornix 提交于
-
- 19 5月, 2020 5 次提交
- 18 5月, 2020 1 次提交
-
-
由 rebornix 提交于
-
- 15 5月, 2020 1 次提交
-
-
由 rebornix 提交于
-
- 14 5月, 2020 4 次提交