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
When hashing file names using [file name].[hash].[file ext] it is possible that trailing characters of the hash + file ext can match a real file and the result will be [file name].[hash].[hash].[file ext] which is problematic.
To fix this, use [hash]-[file name].[file ext] instead when hashing files names.
The text was updated successfully, but these errors were encountered:
updated package dependencies,
now using new format when creating hashed file names,
implemented replacement for replace-in-file,
reduced console.log output,
see issues #14, #15 & #16
jeffschwartz
changed the title
Creating hash file names using [file name].[hash].[file ext] can potentially cause buster to hash the file twice
Creating hash file names using [file name].[hash].[file ext] can potentially cause buster to hash the file name twice
Sep 16, 2019
When hashing file names using
[file name].[hash].[file ext]
it is possible that trailing characters of the hash + file ext can match a real file and the result will be [file name].[hash].[hash].[file ext] which is problematic.To fix this, use [hash]-[file name].[file ext] instead when hashing files names.
The text was updated successfully, but these errors were encountered: