spec-controller 0.1.258 → 0.1.259
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -6
- package/dist/cli.js +107 -644
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -81,19 +81,14 @@ The whole report is written before the exit code is set, so a failing run still
|
|
|
81
81
|
- a mistyped path, or a path it is not permitted to read;
|
|
82
82
|
- a file where a directory belongs, or the reverse;
|
|
83
83
|
- an unparseable report, or a report that parses but is not in the shape its runner writes;
|
|
84
|
-
- a saved reconciliation it cannot render;
|
|
85
84
|
- a corpus the Gherkin parser rejects.
|
|
86
85
|
|
|
87
86
|
The refusal names the input, the path, and what was wrong with it. A well-formed report that holds nothing, such as a Vitest run that matched no test file, is read, not refused.
|
|
88
87
|
|
|
89
|
-
**An output location it cannot write is also `2`**: a `--format` path that is read-only, a directory, under a regular file or in a directory that does not exist
|
|
88
|
+
**An output location it cannot write is also `2`**: a `--format` path that is read-only, a directory, under a regular file or in a directory that does not exist. It is refused before any report is printed, naming the location and the operating system's reason.
|
|
90
89
|
|
|
91
90
|
`--exit-zero` changes `1` and `3` to `0` and leaves every other code alone (see *Report first, gate later*).
|
|
92
91
|
|
|
93
|
-
### Re-rendering a saved report
|
|
94
|
-
|
|
95
|
-
`balance --render-from-json <saved.json>` re-renders a saved report from the same table and exits with the code its verdict names, so a saved run that failed fails again when read back. A report saved under `--strict` records that, so its re-render exits `3` too. `--strict` and `--exit-zero` work beside the re-render as they do on a live run. Any other flag beside it is refused with `2`, because a re-render reads no live input and writes only to stdout.
|
|
96
|
-
|
|
97
92
|
### `allocate`
|
|
98
93
|
|
|
99
94
|
`spec-controller allocate` prints the next claim code for a feature part. It reaches no verdict: it exits `0` when it answers, and `2` for a usage error or an unknown part. A file or directory it cannot read, directly or through git, is a usage error: it is refused, naming the path and the reason, and no code is given.
|