We still use assetic as our main compiler and the file names in compiled dir is clean, except when file masks are used to import multiple files at once, e.g. */*/*/*.js.
Now when we enter the compiled dir or look at the Network tab in Chrome or look at the console errors, stack trace, the file names now look messy. I've also noticed duplicate compiled files with different hash strings.
What do you think about an option to use modification timestamp for cache busting instead of hashes.
What are the advantages of using hash instead of e.g. appending product version ?v4.44 (that we currently use with assetic)?
We still use
asseticas our main compiler and the file names in compiled dir is clean, except when file masks are used to import multiple files at once, e.g.*/*/*/*.js.Now when we enter the
compileddir or look at the Network tab in Chrome or look at the console errors, stack trace, the file names now look messy. I've also noticed duplicate compiled files with different hash strings.What do you think about an option to use modification timestamp for cache busting instead of hashes.
What are the advantages of using
hashinstead of e.g. appending product version?v4.44(that we currently use with assetic)?