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
You can debug with VS Code or Node instead with `jake runtests inspect=true`:
157
+
You can debug with VS Code or Node instead with `gulp runtests --inspect=true`:
158
158
159
159
```Shell
160
-
jake runtests tests=2dArrays inspect=true
160
+
gulp runtests --tests=2dArrays --inspect=true
161
161
```
162
162
163
163
## Adding a Test
@@ -197,20 +197,20 @@ Compiler testcases generate baselines that track the emitted `.js`, the errors p
197
197
When a change in the baselines is detected, the test will fail. To inspect changes vs the expected baselines, use
198
198
199
199
```Shell
200
-
jake diff
200
+
gulp diff
201
201
```
202
202
203
203
After verifying that the changes in the baselines are correct, run
204
204
205
205
```Shell
206
-
jake baseline-accept
206
+
gulp baseline-accept
207
207
```
208
208
209
209
to establish the new baselines as the desired behavior. This will change the files in `tests\baselines\reference`, which should be included as part of your commit. It's important to carefully validate changes in the baselines.
210
210
211
211
## Localization
212
212
213
213
All strings the user may see are stored in [`diagnosticMessages.json`](./src/compiler/diagnosticMessages.json).
214
-
If you make changes to it, run `jake generate-diagnostics` to push them to the `Diagnostic` interface in `diagnosticInformationMap.generated.ts`.
214
+
If you make changes to it, run `gulp generate-diagnostics` to push them to the `Diagnostic` interface in `diagnosticInformationMap.generated.ts`.
215
215
216
216
See [coding guidelines on diagnostic messages](https://github.com/Microsoft/TypeScript/wiki/Coding-guidelines#diagnostic-messages).
0 commit comments