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
Moves fixtures directory to the root, uses file snapshot in unit test,
and creates test helper script for pipeline tests. Updates CONTRIBUTING.
Tests will now all run instead of failing fast.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+8-5
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Contributing
2
2
3
-
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [[RFC2119]][[RFC8174]] when, and only when, they appear in all capitals, as shown here.
3
+
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [[RFC2119]][[RFC8174]] when, and only when, they appear in all capitals, as shown here.
4
4
5
5
## Getting started
6
6
@@ -20,9 +20,12 @@ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "S
20
20
21
21
The [src](./src) directory contains the main and test sources.
22
22
23
-
-[main.js](./src/main.js) represents the entry point (the CLI tool).
24
-
-[generate-declaration.js](./src/generate-declaration.js) represents the unit-tested JS logic.
25
-
-[fixtures](./src/fixtures) directory contains files for data-file-driven unit tests.
23
+
-[main.ts](./src/main.ts) represents the entry point (the CLI tool).
24
+
-[logic.ts](./src/logic.ts) represents the unit-tested logic.
25
+
26
+
The [fixtures](fixtures) directory contains files for data-file-driven unit tests.
27
+
28
+
The [scripts](./scripts) directory contains the esbuild build script and pipeline test helper script.
26
29
27
30
## Expectations
28
31
@@ -31,7 +34,7 @@ All contributions MUST adhere to the following expectations.
31
34
1. Every change MUST have unit tests.
32
35
2. Every change MUST have a GitHub issue linked.
33
36
3. Any configuration option change SHOULD be discussed in a GitHub issue first.
34
-
4. The PR build (see [pipeline.yaml](./.github/workflows/pipeline.yaml)) MUST succeed.
37
+
4. The PR build and test (see [pipeline.yaml](./.github/workflows/pipeline.yaml)) MUST succeed.
35
38
5. I will squash-merge the changeset into `main` upon approval.
0 commit comments