Rails - Mar 2012 - Make Asset Pipeline compatible with Chrome DevTools Autosave

https://github.com/NV/chrome-devtools-autosave doesn’t play nice with Asset 
Pipeline. https://github.com/NV/chrome-devtools-autosave/issues/27

The culprit of the problem is in the asset’s URLs. I cannot decipher a file 
path by its URL. For instance, /assets/main.css?body=1 could be either 
app/assets/stylesheets/main.css, lib/assets/stylesheets/main.css 
or vendor/stylesheets/main.css.

To fix it, we could either make URLs match their file path:
/app/assets/stylesheets/main.css?body=1

or introduce source-path query parameter:
/assets/main.css?body=1&source-path=app/assets/stylesheets/main.css

Any help would be good.

-- 
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/rubyonrails-talk/-/Dak5eruoAyoJ.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.