Stop serving non-digested images in development?

[nfm]

This is a follow up from some of the issues resolved in #84: "Match Dev Asset Experience to Production". This pull request solved issues where assets not flagged to be precompiled would work in development, but then break in production.

I've been having another issue related to development/production parity, where sprockets-rails will happily serve up non-digested images in development if they are statically linked to. This will of course not work in production, as all images are digested.

For example, a JS file might (erroneously) do something like:

$('#something').append("<img src='/assets/logo.png' />");

I'm proposing that we make development behave the same as production, and refuse to serve non-digested images. This could raise an exception or just 404, and could perhaps use the same config flag as #84 does.

I haven't dug into the code yet, but does this sound like something worth putting together a pull request for?

[gjaldon]

That makes sense. Been bit by this recently and shortening the feedback loop so that we know it won't work while still in development would save us devs a lot of time.

Still even having trouble now with my code where I dynamically generate the url to my images in a coffee.erb file. Have code that looks like:
"<%= asset_path('#{fileType}') %>"

It works fine in development but haven't yet figured out why it isn't working production(Heroku). Just saying, would be great if anyone could give insights too.