I've just bumped the version of handlebars_assets used in a Rails project, and noticed that it caused every single asset in the manifest.json to be invalidated, even though the overwhelming majority are unchanged (images, CSS, JS not containing Handlebars or any generated template files).
This line seems to be the culprit — it's effectively invalidating all assets by appending the Handlebars version.
Ideally, incrementing the Handlebars version should only result in a change in affected files (which will be determined automatically by Sprockets).
I've just bumped the version of
handlebars_assets
used in a Rails project, and noticed that it caused every single asset in the manifest.json to be invalidated, even though the overwhelming majority are unchanged (images, CSS, JS not containing Handlebars or any generated template files).This line seems to be the culprit — it's effectively invalidating all assets by appending the Handlebars version.
Ideally, incrementing the Handlebars version should only result in a change in affected files (which will be determined automatically by Sprockets).