@grum-os/cli 0.3.50 → 0.3.52
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 +2 -2
- package/content.md5 +1 -1
- package/grum.mjs +837 -372
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -177,7 +177,7 @@ grum request "color:raw:#3C3C3C" \
|
|
|
177
177
|
|
|
178
178
|
Captures default to the local app. Use `grum request <key> [<key>...] --live` to capture the configured live site after a release. Grum uses the route identified by the finding's source file when it can, otherwise the site's configured URL. This leaves the saved local-app URL unchanged and adds no confirmation prompt. The target URL is printed before capture.
|
|
179
179
|
|
|
180
|
-
`--url` is the page where the element renders, or an HTML file in the repo (`./index.html`) when there is no dev server. An explicit `--url` takes priority over `--live`, including when a shared component needs a specific page. A page behind a login is captured through the
|
|
180
|
+
`--url` is the page where the element renders, or an HTML file in the repo (`./index.html`) when there is no dev server. An explicit `--url` takes priority over `--live`, including when a shared component needs a specific page. A page behind a login is captured through the browser extension in your own browser session. `--browser chrome` or `--browser safari` picks the browser. `--no-capture` sends the request with no picture. For a modal finding, `--open-modal-id <id>` and `--open-trigger-id <id>` explicitly identify the requested modal and its opener. The existing **Scan for review** action opens the requested modal if needed, then captures it. If the modal is already visible, it captures without clicking the opener. It clicks only one unique, visible, enabled button with that id, then captures only after the requested modal is observed open. Submit controls, missing or duplicate ids, and clients without opening support are refused; manual opening and scan retry remain available.
|
|
181
181
|
|
|
182
182
|
```sh
|
|
183
183
|
grum capture reset
|
|
@@ -257,7 +257,7 @@ The menu covers check, setup, and sign-in. These are the same actions as flags,
|
|
|
257
257
|
| `grum doctor [--agent <agent> --json]` | Check setup readiness without changing anything. |
|
|
258
258
|
| `grum scan [--root <dir>]` | Start a fresh scan for the linked workspace and follow its progress. |
|
|
259
259
|
| `grum check [flags]` | Check the working tree. See the flags below. |
|
|
260
|
-
| `grum request <key> [<key>...] [--reason "..."] [--url <page>] [--live] [--browser chrome | safari] [--no-capture]`
|
|
260
|
+
| `grum request <key> [<key>...] [--reason "..."] [--url <page>] [--live] [--browser chrome | safari] [--open-modal-id <id> --open-trigger-id <id>] [--no-capture]` | Ask the owners to allow drift items; items on one page capture together. |
|
|
261
261
|
| `grum add-token ...` / `grum add-button ...` | For owners, add a token or approved button design to the contract. |
|
|
262
262
|
| `grum add-icon <ref> [--name <name>]` | For owners, add an icon `grum check --json` lists under `discovered.icons`, from this checkout's source. |
|
|
263
263
|
| `grum snooze <key> [<key>...]` | Pause questions about existing drift on this branch for the configured period. |
|
package/content.md5
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
|
|
1
|
+
a1c26d17484f1578c628a91e8733a823
|