@datarails-ai/dr-appspace-cli 0.12.58 → 0.12.59
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 +18 -1
- package/dist/cli.js +1603 -538
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -344,6 +344,7 @@ then reads each laid-out page back for the `look-*` findings below.
|
|
|
344
344
|
| `--width <px>` / `--height <px>` | the window | `1400` × `900` |
|
|
345
345
|
| `--full` | grow the window to the page's full height (one extra load per picture) | off |
|
|
346
346
|
| `--no-look` | skip the look load (see below) | look on |
|
|
347
|
+
| `--no-sample` | answer data cards with `tests.json` or `[]` only (see below) | sample on |
|
|
347
348
|
| `--shelf <path>` | serve `vendor/` and `ui-kit/` from this dr-app-space checkout | the server the app is pushed to |
|
|
348
349
|
| `--screenshot-budget <ms>` | the whole phase's ceiling; each picture is capped at 60 s | `180000` |
|
|
349
350
|
|
|
@@ -385,6 +386,19 @@ the tenant's rows, so a page can lay out differently with real data. Without
|
|
|
385
386
|
`--screenshot-budget`, so they never cost a picture; one with less than 5 s
|
|
386
387
|
left is skipped and its row says why in `lookSkipped`.
|
|
387
388
|
|
|
389
|
+
**Data cards draw on sample data.** A card the page's contract ties to data
|
|
390
|
+
is answered with a sample payload of its kind when `tests.json` holds no
|
|
391
|
+
value for it: a dashboard's cards (the SPEC handler's `load`, and its
|
|
392
|
+
`catalog`, so the filter bar draws its chips and selects) and an app's
|
|
393
|
+
`widget` elements (their handler, read as their kind reads). The payloads
|
|
394
|
+
are the widget contract's own fixtures, scaled per card the same way every
|
|
395
|
+
run, so a picture shows the cards a viewer meets instead of failure panels.
|
|
396
|
+
They are never the tenant's figures and never a fixture assertion. A
|
|
397
|
+
hand-written `expect` still wins; lists, grids and action handlers keep
|
|
398
|
+
`tests.json` or `[]`. The table names the sampled handlers, each picture's
|
|
399
|
+
row in `index.json` lists them in `handlersSampled`, and `--no-sample`
|
|
400
|
+
turns it off.
|
|
401
|
+
|
|
388
402
|
**The same check on the kit goldens, in CI.** The "Golden look" job in
|
|
389
403
|
`pr-checks.yml` draws every kit golden and test app the same way, offline, at
|
|
390
404
|
the kit's pins and at the newest `dr-app-*` release on the shelf, and fails on
|
|
@@ -394,7 +408,10 @@ move, not a builder. To try a release by hand, from `cli/`:
|
|
|
394
408
|
fails on B6).
|
|
395
409
|
|
|
396
410
|
Chrome is found through `CHROME_PATH`, then `google-chrome`, `chromium` or
|
|
397
|
-
`chrome` on `PATH`, then the macOS app bundle and the usual Linux paths
|
|
411
|
+
`chrome` on `PATH`, then the macOS app bundle and the usual Linux paths
|
|
412
|
+
(`/opt/google/chrome/chrome` included, where the managed build sandbox keeps
|
|
413
|
+
its Chromium). Run as root, as a container's shell is, Chrome gets
|
|
414
|
+
`--no-sandbox`, which it needs to start there. With
|
|
398
415
|
none, the command exits 2 before anything runs. No browser is ever
|
|
399
416
|
downloaded. Each Chrome gets its own temporary profile, which is removed
|
|
400
417
|
afterwards, and its process group is killed once the file is written,
|