Previously we were using the files collection which contains all versions of all digest assets sorted chonologically. This meant that if an asset was reverted to a previous state (by git revert for instance) then the non-digest version of the asset would end up being the wrong version. See #42 for additional details on the problem.
By iterating over the assets hash instead of files we make sure that we're using the digest versions that the app considers to be "current". A nice side effect is that we also end up copying fewer files.
Previously we were using the
files
collection which contains all versions of all digest assets sorted chonologically. This meant that if an asset was reverted to a previous state (bygit revert
for instance) then the non-digest version of the asset would end up being the wrong version. See #42 for additional details on the problem.By iterating over the
assets
hash instead offiles
we make sure that we're using the digest versions that the app considers to be "current". A nice side effect is that we also end up copying fewer files.Fixes #42