058e781b3f
Await newly promisified func
2021-03-01 16:39:57 -06:00
a83c909b16
fix: update deps import in coder.js
2021-02-26 16:46:20 -07:00
9dea2e79a0
chore: fix lint issues
2021-02-26 15:48:04 -07:00
1bf3036597
fix(connection): onClose -> onDidDispose protocol
2021-02-26 12:55:04 -07:00
52acb50ed7
fix: update WebSocketNodeSocket in protocol
2021-02-26 12:54:29 -07:00
22e7173fa9
fix: update resolveCommonProperties in server
2021-02-26 12:54:03 -07:00
0f18d1fddc
fix: update import in channel.ts getSystemShell
2021-02-25 16:44:08 -07:00
b71c5061e1
chore: update electron types
2021-02-25 16:43:53 -07:00
b7e112a78d
chore: reorder package.json lib/vscode
2021-02-25 16:43:45 -07:00
e002f14423
revert: turn off two rules in eslint for vscode
2021-02-25 12:41:15 -07:00
c6e6f8e2b3
chore: add missing semicolon in channel.ts
2021-02-25 12:41:01 -07:00
1b9ed6eea3
chore: update yarn.lock for vscode
2021-02-25 12:31:20 -07:00
6a6ab72414
fix: resolve conflicts in eslintrc.json
...
It looks like they turned some eslint warnings on. Or we had them off and I
turned them on. They also added a new target which had the name monaco in it.
2021-02-25 12:25:28 -07:00
ccf2fe2a2e
fix: conflicts in remote.ts
...
Looks like they modified a few of the cases related to Reconnection.
2021-02-25 12:23:14 -07:00
502323a9c8
fix: conflicts with remoteAgentConnection
...
As Asher pointed out, looks like it makes #2381 obsolete.
Hope this all works.
2021-02-25 12:19:21 -07:00
f214235e2d
fix: resolve conflicts in build/lib/node.ts
...
It looks like they added a few more variables and cleaned this file up.
I removed the yarn and yarnRc stuff. Hope that doesn't break anything.
2021-02-25 12:08:12 -07:00
40d0c88341
fix: extHostExtensionService
...
Looks like they modified the function signature for _loadCommonJSModule.
I believe the first param is now the extensionId or null. Probably for logging
reason guessing.
2021-02-25 12:02:35 -07:00
2bd9b6e1bf
fix: update web.main.ts
...
Looks like they added two lines in the open method.
1. Logging for workbench configuration
2. Window - creating a BrowserWindow
2021-02-25 11:59:25 -07:00
ce1a8c89dd
fix: postinstall.js conflicts
...
Again, hope this was correct.
It looks like they moved around a few lines here.
If there are issues with dependencies not installing, check here.
2021-02-25 11:57:35 -07:00
9e61540840
fix: resolve conflicts in package.json
...
I hope this was done correctly.
It upgraded a few packages, we left out the electron packages and it added two
resolutions.
2021-02-25 11:52:27 -07:00
b952616725
fix: resolve conflict browserSocketFactory
2021-02-25 11:47:02 -07:00
3fd6187503
fix: update import in extensionsViewlet
2021-02-25 11:46:25 -07:00
f255cdb2cc
fix: update text for Extension Host
2021-02-25 11:44:37 -07:00
262963c9ec
fix: resolve conflict in extensionHostProcessSetup.ts
...
From what I can tell, they added these `performance.mark` calls. Not sure
exactly what they do, but my guess is they're supposed to help with measuring
extension performance?
2021-02-25 11:42:42 -07:00
7bf1fd979e
fix: resolve conflicts in yarn.lock
2021-02-25 11:41:34 -07:00
2c5c48525e
fix: resolve conflicts in .eslintignore
2021-02-25 11:36:01 -07:00
c94697da98
fix: resolve conflicts in .gitignore
2021-02-25 11:35:23 -07:00
eae5d8c807
chore(vscode): update to 1.53.2
...
These conflicts will be resolved in the following commits. We do it this way so
that PR review is possible.
2021-02-25 11:27:27 -07:00
271c260a36
Fix terminal process leak when closing the window. ( #2723 )
2021-02-22 13:32:50 -06:00
8302d2fe8e
fix(vscode): update links in welcome page
2021-02-18 11:21:27 -07:00
43d0d8e919
fix: update link in extensions helper
2021-02-18 10:54:45 -07:00
898565e16a
Resolve browser telemetry conflict
2021-02-09 11:11:38 -06:00
948e01fb27
Bundle jpg from VS Code
...
These seem to be used in some "getting started" page but I'm not sure
where it is.
2021-02-09 11:11:17 -06:00
068e399bf2
Remove Node browser shim
...
We used this to run vscodevim in the browser but it now has a version
that is able to run as a VS Code web extension. This does require an
update to our marketplace, however.
2021-02-09 10:40:14 -06:00
a65231808a
Fall back to remote extension server on web
2021-02-09 10:39:35 -06:00
a6d4b24733
Resolve extensions viewlet conflicts
2021-02-09 10:39:08 -06:00
f8d546bdc6
Remove hidden home CSS
...
Now that you can customize the home it's probably fine to show it.
There's also an option for users to hide it.
2021-02-09 10:38:14 -06:00
cc59279f11
Remove GoHomeContributor
...
It's probably registered in some other way now.
2021-02-09 10:37:03 -06:00
89c38d3554
Update storage promise
...
A new doStore was added.
2021-02-09 10:36:39 -06:00
14c96d78ef
Remove added logLevel
...
We've always had this.
2021-02-09 10:33:11 -06:00
80d50057fc
Remove electron and resolve yarn.lock conflict
2021-02-09 10:32:27 -06:00
0a1a8fe4fe
Remove new .yarnrc
2021-02-09 10:19:24 -06:00
9221efc104
Restore Node check
...
Since we're following the VS Code allowed version range now to prevent
bugs use the new range instead of commenting it out.
2021-02-09 10:09:45 -06:00
859de79d97
Update to VS Code 1.52.1
2021-02-09 16:08:37 +00:00
1fcb0c3ddd
Merge pull request #2641 from cdr/send-ready-to-all-origins
...
Send 'loaded' event to all parent origins
2021-01-27 05:52:13 +10:00
42dcfc94ab
Send 'loaded' event to all parent origins
2021-01-27 05:06:04 +10:00
883dd13850
refactor: move jest and add package.json to /test
2021-01-21 14:06:49 -07:00
0a07d67c8d
fix: prevent mocha/jest types conlict
...
Modify the tsconfig.json in lib/vscode/src/build.
This adds the flag skipLibCheck: true to tell TypeScript
to not type-check the declaration files at build time.
We need to add this because otherwise it checks the declaration
files and reports an error of duplicate type definitions
because we use Jest for our tests and they use Mocha and they
both use the global namespace "test" in their .d.ts files.
2021-01-21 10:11:09 -07:00
500ba92466
fix: style links with correct colors
2021-01-14 22:40:33 +00:00
d9508946b5
feat: add helper header above extensions search
...
Add a short message above the search box on the Extensions panel. This
helps explain the extension divergence to the user.
If they click dismiss, it stores an item in localStorage to prevent the
message from showing up on subsequent loads.
Co-authored-by: Asher <ash@coder.com>
2021-01-14 22:40:19 +00:00
Asher
Joe Previte
Adrian Soucup
Dean Sheather