Page MenuHomePhabricator

Fix deletion detection when updating based on ZIP
ClosedPublic

Authored by hach-que on Dec 7 2013, 6:32 AM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Jan 28, 6:04 AM
Unknown Object (File)
Sat, Jan 25, 12:39 AM
Unknown Object (File)
Sat, Jan 18, 8:13 AM
Unknown Object (File)
Sat, Jan 18, 2:04 AM
Unknown Object (File)
Mon, Jan 13, 12:04 AM
Unknown Object (File)
Dec 15 2024, 5:49 PM
Unknown Object (File)
Dec 13 2024, 7:58 PM
Unknown Object (File)
Dec 11 2024, 6:30 PM

Details

Reviewers
epriestley
Group Reviewers
Blessed Reviewers
Maniphest Tasks
T4205: Implement Phragment
Commits
Restricted Diffusion Commit
rP67b37a5c1dc0: Fix deletion detection when updating based on ZIP
Summary

When the code to update based on ZIP went to look up the child fragments, it explicitly used the paths provided in the ZIP. This meant that we could never detect omissions because there'd never be a scenario where a child fragment would return but not exist in the ZIP. To fix this, the query should be using withLeadingPath instead of withPaths.

Test Plan

Uploaded a ZIP that omitted a file and saw the deleteFile get called (by placing debugging output in the code).

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped