Repository navigation
1.5.2
-
A pull no longer rewrites a file item's wrapper that already says what Canvas
says. A pull that brought down the binary regenerated the wrapper beside it as
well, so one whose title andfile_refhad not changed still came back
normalised:title: 'Syllabus'lost its quotes, a file without a final
newline gained one, keys were reordered and any body was dropped. The wrapper
is now rewritten only when its title, its type or the path itsfile_ref
resolves to would read differently. Afile_refinto the shared
course/_files/folder is still repointed at the module-local copy, as
before. -
Publishing or unpublishing a module in Canvas no longer makes the file items
in it read as changed on Canvas. Canvas locks a file when its module is
unpublished and unlocks it on publish, and each lock moves the file's
updated_at, which a file item's fingerprint hashed. So after one publish
click the next pull or sync downloaded every binary in the module again and,
before the entry above, rewrote its wrapper as well. A file item is now
fingerprinted by the file'smodified_at, which moves only when the file's
content is replaced, and thenewestconflict tiebreak reads the same
timestamp, so a publish click no longer makes Canvas look newer than a binary
replaced here.The first pull, push or sync after updating re-records the fingerprint of
every file item in.canvas-sync.jsonand touches nothing else, so expect a
diff in that file worth committing. A file item whose module was published or
unpublished since the last sync reads as changed on Canvas that one time, as
it would have without the update: the publish moved theupdated_atthe old
fingerprint was taken from.