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
+4-4
Original file line number
Diff line number
Diff line change
@@ -121,9 +121,9 @@ and exposed an API to the front-end for file access and all UI needs.
121
121
122
122
Over time, Microsoft added support to VS Code to run it on the web. They have made
123
123
the front-end open source, but not the server. As such, code-server v2 (and later) uses
124
-
the VS Code front-end and implements the server. We use a git subtree to be able to pull in VS Code's front-end. This code lives under [./lib/vscode](./lib/vscode).
124
+
the VS Code front-end and implements the server. We do this by using a git subtree to fork and modify VS Code. This code lives under [./lib/vscode](./lib/vscode).
125
125
126
-
Some noteworthy changes in our codebase:
126
+
Some noteworthy changes in our version of VS Code:
127
127
128
128
- Adding our build file, which includes our code and VS Code's web code
129
129
- Allowing multiple extension directories (both user and built-in)
@@ -138,8 +138,8 @@ Some noteworthy changes in our codebase:
138
138
- Adding connection type to web socket query parameters
139
139
140
140
As the web portion of VS Code matures, we'll be able to shrink and possibly
141
-
eliminate our patch. In the meantime, upgrading the VS Code version requires
142
-
us to ensure that our changes are applied and work as intended. In the future,
141
+
eliminate our modifications. In the meantime, upgrading the VS Code version requires
142
+
us to ensure that our changes are still applied and work as intended. In the future,
143
143
we'd like to run VS Code unit tests against our builds to ensure that features
0 commit comments