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: README.md
+20-6
Original file line number
Diff line number
Diff line change
@@ -24,19 +24,19 @@ Then, leetcode-practice will meet all your needs!
24
24
25
25
The best and most flexible way to use it is to use our CLI in the terminal. You can create and check your solutions using three core commands: `lk`, `lf`, and `lc`.
You can also use GitHub's fork feature to create a copy of our project. Then, you can directly use the built-in commands within the project to create and check solutions.
You can also use our `leetcode-practice` plugin available in the plugin marketplace for interactive creation and checking of solutions. (Supported on two popular editors: `WebStorm` and `VS Code`)
Type `lk` followed by the `-e` parameter in the terminal to use interactive mode for checking the problem.
281
+
277
282
```shell
278
283
# Full command
279
284
lk -e
@@ -334,6 +339,7 @@ Note: Unable to execute test cases in this environment.
334
339
335
340
The `create` and `check` commands can also use the `-d` parameter to specify a relative address based on the current working directory as the specified directory.
336
341
When specifying a directory, the operation will be performed in that directory.
342
+
337
343
```shell
338
344
# Use the src directory as the generation directory
Using the `-u` or `--update` parameter, you can check whether the current version is the latest version. If the current version is not the latest version, you will be prompted whether to update.
384
+
378
385
```shell
379
386
lk -u
380
387
lf -u
381
388
lc -u
382
389
```
390
+
383
391
```shell
384
392
? Automatically detected environment is [ project ], if not, please make a selection, if yes, please press Enter to confirm. project
385
393
Start getting version number in npm repository...
@@ -412,14 +420,17 @@ The commands in the forked project are the same as those in the CLI usage parame
412
420
413
421
##### [1]. Create Solution [`lc`]
414
422
415
-
Refer to the `lc` part of the CLI for parameters: [lc](#1-Creating-Solutions---lc)
423
+
Refer to the `lc` part of the CLI for parameters: [lc](#1-creating-solutions---lc)
416
424
417
425
Simple usage example:
426
+
418
427
```shell
419
428
# Execute using yarn
420
429
yarn lc 1314
421
430
```
431
+
422
432
Execution result:
433
+
423
434
```shell
424
435
# Generated in the src directory
425
436
> yarn lc 1314
@@ -433,14 +444,17 @@ Problem file address is:/Users/mac-106/wh131462/workspace/leetcode-practice/src/
433
444
434
445
##### [2]. Check Solution [`lk`]
435
446
436
-
Refer to the `lk` part of the CLI for parameters: [lk](#2-Checking-Solutions---lk)
447
+
Refer to the `lk` part of the CLI for parameters: [lk](#2-checking-solutions---lk)
437
448
438
449
Simple usage example:
450
+
439
451
```shell
440
452
# Execute using yarn
441
453
yarn lk 1314
442
454
```
455
+
443
456
Execution result:
457
+
444
458
```shell
445
459
# Checked in the src directory
446
460
> yarn lk 1314
@@ -460,7 +474,7 @@ Click to jump to problem submission: https://leetcode.com/problems/matrix-block-
460
474
461
475
##### [3]. Look Up Solutions [`lf`]
462
476
463
-
Refer to the `lf` part of the CLI for parameters: [lf](#3-Problem-Lookup---lf)
477
+
Refer to the `lf` part of the CLI for parameters: [lf](#3-problem-lookup---lf)
0 commit comments