You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
--simulate-json follow-ups considered and deferred #37
Ideas from the #27 reviews and the size analysis that were deliberately left out:
Make files an object keyed by path. JsonObjectAppendElement would de-duplicate for free and sort the output. It is a schema change, and arrays are more conventional.
If PR 1 is still too big for a maintainer, split its file metadata into a follow-up: first path + change, then type, permissions, uid, gid, size, sha256 and target.
Style nits from the Fable review: JsonArrayAppendPkgOperations() sits in libntech's JsonArrayAppend* namespace while its siblings are Add*ToJson(). create_chroot_file() in the unit test relies on EVAL_MODE to redirect MakeParentDirectory(), where MakeParentInternalDirectory(chrooted) would be explicit.
The all-zero-digest check is now compact. The alternative was to drop it and match the other HashFile() callers.
Activity