Skip to content

1.5.3

Choose a tag to compare

@github-actions github-actions released this 02 Oct 06:42
· 22 commits to main since this release
6ad6184
  • A pull now downloads a file item's binary onto the path its file_ref names
    when that path is inside a _files/ folder under course/, and leaves the
    file_ref as 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-build writes one, was pointed at a
    second copy in a new _files/ inside the subfolder, and a file_ref into the
    shared course/_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_ref that leaves course/ 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/:id link
    and completion requirement, and the next status or sync read 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.