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 doing an assetic dump, the same file names are used every time you do a dump. This could potentially cause issues if a file is cached and the CSS source has been updated. Would it be possible to compare the code of what is about to be dumped into the file with the code that is already in there and then if it is different, delete the old file and create a new one with a different name?
This would mean that every time you do a dump, every asset that has been modified (the resulting asset, adding comments etc won't make a difference if you are minimizing) would change names and when the browser loads the CSS you would know its loading the new version.
The text was updated successfully, but these errors were encountered:
When doing an assetic dump, the same file names are used every time you do a dump. This could potentially cause issues if a file is cached and the CSS source has been updated. Would it be possible to compare the code of what is about to be dumped into the file with the code that is already in there and then if it is different, delete the old file and create a new one with a different name?
This would mean that every time you do a dump, every asset that has been modified (the resulting asset, adding comments etc won't make a difference if you are minimizing) would change names and when the browser loads the CSS you would know its loading the new version.
The text was updated successfully, but these errors were encountered: