You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/CONTRIBUTING.md
+13-10
Original file line number
Diff line number
Diff line change
@@ -2,13 +2,14 @@
2
2
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
3
3
# Contributing
4
4
5
-
-[Pull Requests](#pull-requests)
6
-
-[Requirements](#requirements)
7
-
-[Development Workflow](#development-workflow)
8
-
-[Build](#build)
9
-
-[Structure](#structure)
10
-
-[VS Code Patch](#vs-code-patch)
11
-
-[Currently Known Issues](#currently-known-issues)
5
+
-[Contributing](#contributing)
6
+
-[Pull Requests](#pull-requests)
7
+
-[Requirements](#requirements)
8
+
-[Development Workflow](#development-workflow)
9
+
-[Build](#build)
10
+
-[Structure](#structure)
11
+
-[VS Code Patch](#vs-code-patch)
12
+
-[Currently Known Issues](#currently-known-issues)
12
13
13
14
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
14
15
@@ -126,7 +127,7 @@ and exposed an API to the front-end for file access and all UI needs.
126
127
127
128
Over time, Microsoft added support to VS Code to run it on the web. They have made
128
129
the front-end open source, but not the server. As such, code-server v2 (and later) uses
129
-
the VS Code front-end and fills in with the server. You can find this in
130
+
the VS Code front-end and implements the server. You can find this in
130
131
[./ci/dev/vscode.patch](../ci/dev/vscode.patch) under the path `src/vs/server`.
131
132
132
133
Other notable changes in our patch include:
@@ -144,8 +145,10 @@ Other notable changes in our patch include:
144
145
- Adding connection type to web socket query parameters
145
146
146
147
As the web portion of VS Code matures, we'll be able to shrink and possibly
147
-
eliminate our patch. In the meantime, upgrading the VS Code version requires us to ensure that the patch is applied and works as intended. In the future, we'd like to run VS
148
-
Code unit tests against our builds to ensure that features work as expected.
148
+
eliminate our patch. In the meantime, upgrading the VS Code version requires
149
+
us to ensure that the patch is applied and works as intended. In the future,
150
+
we'd like to run VS Code unit tests against our builds to ensure that features
0 commit comments