## Commits to load to setup the test runner. Optional.
42
42
setup:
43
-
## A list of commits to load to setup the tutorial
44
-
commits:
45
-
- commit1
46
-
- commit2
47
43
## A list of commands to run to configure the tutorial
48
44
commands:
49
45
- npm install
@@ -57,7 +53,7 @@ config:
57
53
## The uri path to the repo containing the code commits. Required.
58
54
uri: https://.com/coderoad/fcc-learn-npm
59
55
## The branch on the repo uri that contains the code commits. Required.
60
-
branch: v0.3.0
56
+
branch: v0.4.1
61
57
## A list of tutorial dependencies to ensure the environment is setup for the tutorial. Optional.
62
58
## The dependencies will be checked by running `dependency.name` --version and comparing it to the version provided.
63
59
##
@@ -68,31 +64,23 @@ config:
68
64
version: '>=10'
69
65
## A level is made up of
70
66
levels:
71
-
- id: L1
67
+
- id: '1'
72
68
steps:
73
69
## Example 1: Opening files
74
-
- id: L1S1
70
+
- id: '1.1'
75
71
## Setup for the first task. Required.
76
72
setup:
77
73
## Files to open in a text editor when the task loads. Optional.
78
74
files:
79
75
- package.json
80
-
## Commits to load when the task loads. These should include failing tests. Required.
81
-
commits:
82
-
- commit3
83
76
## Solution for the first task. Required.
84
77
solution:
85
78
## Files to open when the solution loads. Optional.
86
79
files:
87
80
- package.json
88
-
## Commits that complete the task. All tests should pass when the commits load. These commits will not be loaded by the tutorial user in normal tutorial activity.
89
-
commits:
90
-
- commit4
91
81
## Example Two: Running commands
92
-
- id: L1S2
82
+
- id: '1.2'
93
83
setup:
94
-
commits:
95
-
- commit5
96
84
## CLI commands that are run when the task loads. Optional.
97
85
commands:
98
86
- npm install
@@ -102,12 +90,10 @@ levels:
102
90
commands:
103
91
- npm install
104
92
## Example Three: Watchers
105
-
- id: L1S3
93
+
- id: '1.3'
106
94
setup:
107
95
files:
108
96
- package.json
109
-
commits:
110
-
- commit7
111
97
## Listeners that run tests when a file or directory changes.
112
98
watchers:
113
99
- package.json
@@ -118,25 +104,14 @@ levels:
118
104
commits:
119
105
- commit8
120
106
## Example Four: Subtasks
121
-
- id: L1S4
107
+
- id: '1.4'
122
108
setup:
123
-
commits:
124
-
- commit8
125
109
commands:
126
110
## A filter is a regex that limits the test results
127
111
- filter: '^Example 2'
128
112
## A feature that shows subtasks: all filtered active test names and the status of the tests (pass/fail).
0 commit comments