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
+27-3Lines changed: 27 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,31 @@ Book Samples
5
5
6
6
Each chapter has its own folder, which will correspond to the zip file name for that chapter on submission.
7
7
Within each chapter folder is a folder for each sample. The folder should contain enough to run the sample independent of the other samples, including tests.
8
-
I have put an index (i.e. 01, 02, etc.) in front of each sample so that you can see the order in which they appear in the chapter.
9
-
Where the sample has a corresponding Plunk, I have added the Plunk ID in brackets after the name of the sample in the folder name.
8
+
There is an index (i.e. 01, 02, etc.) in front of each sample so that you can see the order in which they appear in the chapter.
9
+
Where the sample has a corresponding Plunk, the Plunk ID is added in brackets after the name of the sample in the folder name.
10
10
11
-
We could have a common folder for libraries that we can pull from a CDN.
11
+
## Library files
12
+
13
+
There is a common folder for libraries called lib.
14
+
15
+
## Testing
16
+
17
+
There is a basic grunt file that can run all the unit tests.
18
+
19
+
You need to install the grunt command line globally:
20
+
21
+
```
22
+
npm -g install grunt-cli
23
+
```
24
+
25
+
and grunt itself locally (using the values in the package.json):
26
+
27
+
```
28
+
npm install grunt
29
+
```
30
+
31
+
Run the test task on grunt to execute all the samples' tests.
0 commit comments