Repository navigation
1.5.3
-
A pull now downloads a file item's binary onto the path its
file_refnames
when that path is inside a_files/folder undercourse/, and leaves the
file_refas written. It used to download into the_files/beside the
wrapper, under the Canvas file's name, and repoint the wrapper there. So a
wrapper in a subfolder that names the module's own folder as
../_files/pack.md, the way/study-pack-buildwrites one, was pointed at a
second copy in a new_files/inside the subfolder, and afile_refinto the
sharedcourse/_files/was pointed at a module-local copy. The filename is
kept too, so a file renamed in Canvas no longer leaves the old copy behind. A
file_refthat leavescourse/or points outside every_files/folder is
still repointed, because the bytes come from Canvas and could otherwise land
over a page. -
Pushing a file item whose binary you edited keeps its module item. Canvas
gives new bytes uploaded under the same name a new file id and repoints the
module item at it by itself, but a push read the new id as a renamed binary,
deleted the module item and created another at the end of the module. So every
edited binary cost its item the id, and with it any/modules/items/:idlink
and completion requirement, and the nextstatusorsyncread the move as
Canvas reordering the module and offered to renumber the local files to match.
A push now reads the module item after the upload and leaves one Canvas
already repointed alone. A renamed binary still gets a new module item, now at
the position the old one held.