Photo.savePath docs: a live photo not yet stored may move
check / check (push) Successful in 1m47s

For a live photo the backup has not stored, savePath carries the
title's extension, and the backup may store the image under the one
found inside the live photo. The comment on Photo.savePath and the
README now say so, as the comment on ContentCache.savePath does.

Model: opus-5-5
This commit is contained in:
2026-10-01 15:35:38 +00:00
parent ead27ff419
commit 824b2dbd76
2 changed files with 10 additions and 7 deletions
+5 -4
View File
@@ -699,10 +699,11 @@ synchronous getters look at the disk and never touch the network:
- `photo.savePath` → `string | undefined` — where `lib.backup()` writes the
original, `originals/<fileID>.<ext>` under the `downloadDirectory` the library
was opened with, whether or not it is there yet. For a live photo the backup
has stored, it is the image's path, whose extension comes from inside the live
photo and can differ from the title's. `undefined` when the library has no
`downloadDirectory` or no content source.
was opened with, whether or not it is there yet: for a live photo already
stored, its image. For a live photo not yet stored, it carries the title's
extension, and the backup may store the image under a different one, found
inside the live photo. `undefined` when the library has no `downloadDirectory`
or no content source.
- `photo.isLocal` → `boolean` — whether the whole original is at `savePath`.
Four async methods may download: