apple-journal-cli 1.4.3 → 1.4.5
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 +3 -2
- package/bin/journal-cli +0 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -218,7 +218,7 @@ humans:
|
|
|
218
218
|
| `--dry-run` | every mutating command can print its plan and write nothing |
|
|
219
219
|
| `--live` gate | writes to the real store refuse to run without it |
|
|
220
220
|
| App check | writes refuse to run while Journal.app is open |
|
|
221
|
-
| Auto-backup | every live write backs the store up to its own folder in `~/Backups/journal-cli/` first, and is refused if that fails. Media that `edit --remove-media`, `delete --hard` or `empty` removes is moved into that backup's `Attachments/` after the write commits, so restoring the backup restores the files too |
|
|
221
|
+
| Auto-backup | every live write backs the store up to its own folder in `~/Backups/journal-cli/` first, and is refused if that fails. Media that `edit --remove-media`, `delete --hard` or `empty` removes is moved into that backup's `Attachments/` after the write commits, so restoring the backup restores the files too. Backups restore *in place*: they hold the database and the media a write removed, not a copy of the whole attachment library or `.moments_SUPPORT` (which journal-cli never deletes) |
|
|
222
222
|
| Body input | an unreadable or non-UTF-8 `--body-file` (or stdin) is an error, never an empty body; an empty file still clears the text on purpose |
|
|
223
223
|
| Failed writes | a write that fails part way rolls back and removes any attachment folders it created; files it was going to remove stay until the commit |
|
|
224
224
|
| Synced hard-deletes | refused without `--force`: a local row delete does not tombstone the CloudKit record, and the entry **resurrects on the next sync** (observed). Soft delete syncs properly. |
|
|
@@ -343,7 +343,8 @@ tests/test_write.sh # full suite against a store copy
|
|
|
343
343
|
|
|
344
344
|
`JOURNAL_BACKUP_DIR=DIR` sends backups to `DIR` instead of
|
|
345
345
|
`~/Backups/journal-cli/`, and makes sandbox writes take one too, which is how
|
|
346
|
-
the suite tests backups.
|
|
346
|
+
the suite tests backups. `JOURNAL_PHOTOS_DB=FILE` points `--photos-link` at
|
|
347
|
+
another Photos library database.
|
|
347
348
|
|
|
348
349
|
The `reference/` directory holds the original Python implementation — same
|
|
349
350
|
command surface, same test suite, useful for spelunking since it needs no
|
package/bin/journal-cli
CHANGED
|
Binary file
|