bertramdev/asset-pipeline — pull request #47 by leonli (2013-12-09 08:01:33+00:00)
Title: Should add a config parameter to disable the CssProcessor and Image Taglib for processing the versioning of images

The plugin is awesome, I'm using it to replace the complicated official plugin of "resources".
But I think the plugin could do its job better by disabling image versioning.
Versioning CSS and JSs files are awesome for the modern web, but image files? I don't think the web developer will change the image or background during the production mode. They will just add new image/background with new name to the project. Which means the static file of images are not need to be rotated their versions.

And the versioning of image files meet an issue to my project. I'm developing a modern web application which should be able to support both normal display and retina display, and I'm using a JS library to do the job named "retina_replace". The plugin works automatically, we just need to follow the rule which is naming the 2x pictures xxxx_2x.png. However, the assets plugin will version image files in production module, then all _2x.png files will be returned HTTP 404. I have modified the code of the plugin to resolve the issue of my project. But I think versioning image files may be not really make sense to the web developer.

I would highly recommend to add a parameter to the config.groovy file, which is able to disable the CssProcessor and Taglib to process the versioning of images.

Best Regards,

Leon