Skip to content

Commit c43c135

Browse files
committed
style: typos
1 parent 804fc11 commit c43c135

3 files changed

Lines changed: 8 additions & 8 deletions

File tree

e2e/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@
44
## Directory structure
55

66
- `__cases__`: each scenario/minimal repo is in a sub-folder of this one
7-
- `__templates__`: contains the package dependency tempaltes for test cases
8-
- `__templates__/default`: is the default tempalte
7+
- `__templates__`: contains the package dependency templates for test cases
8+
- `__templates__/default`: is the default template
99
- `__tests__`: contains the actual tests
1010
- `__e2e_workdir_link__`: is created during a test run and is a symbolic link to a subfolder in the temp folder of the OS where all test cases are installed
1111

e2e/__templates__/README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
1-
# E2E package-set tempaltes
1+
# E2E package-set templates
22

33
Each directory must contain a `package.json` and `package-lock.json`.
44

5-
To use it as a tempalte in your test case, add `"e2eTemplate": "my-template-dir"` in the `package.json` of your test case.
5+
To use it as a template in your test case, add `"e2eTemplate": "my-template-dir"` in the `package.json` of your test case.
66

77
Normally you should not worry and only use the default template (which is what happen if you do not set any `e2eTemplate` key). But in some test case you might want to have a specific package installed. Then you first look for a directory containing a `package.json` with dependencies you want, and if there isn't, you create one by duplicating the `default` (more explanation below).
88

99
## Creating a template
1010

11-
Let's say you want to create a template with the `lodash` package and call the tempalte `with-lodash` (surprising name, I know):
11+
Let's say you want to create a template with the `lodash` package and call the template `with-lodash` (surprising name, I know):
1212

1313
1. `cd e2e/__templates__`
1414
2. `mkdir with-lodash`
@@ -20,7 +20,7 @@ Let's say you want to create a template with the `lodash` package and call the t
2020
That's it, the template is ready to be used
2121

2222

23-
## Using a specific tempalte
23+
## Using a specific template
2424

2525
Let's say you want to use your lately created `with-lodash` template in a `using-lodash` test case:
2626

scripts/e2e.js

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ function setupE2e() {
2323
// ensure directory exists before copying over
2424
fs.mkdirpSync(Paths.e2eWorkTemplatesDir);
2525

26-
// create the tempalte packages from which node_modules will be originally copied from
26+
// create the template packages from which node_modules will be originally copied from
2727
fs.copySync(
2828
path.join(Paths.e2eTemplatesDir),
2929
path.join(Paths.e2eWorkTemplatesDir)
@@ -46,7 +46,7 @@ function setupE2e() {
4646
// copy source and test files
4747
fs.copySync(path.join(Paths.e2eSourceDir, directory), caseDir);
4848

49-
// grab the tempalte name to be used
49+
// grab the template name to be used
5050
const template =
5151
require(path.join(caseDir, 'package.json')).e2eTempalte || 'default';
5252

0 commit comments

Comments
 (0)