Skip to content
This repository has been archived by the owner on Jun 10, 2018. It is now read-only.

Compatibility with Chrome DevTools Autosave #307

Closed
NV opened this issue Mar 17, 2012 · 4 comments
Closed

Compatibility with Chrome DevTools Autosave #307

NV opened this issue Mar 17, 2012 · 4 comments

Comments

@NV
Copy link

NV commented Mar 17, 2012

Chrome DevTools Autosave doesn’t work with Sprockets (NV/chrome-devtools-autosave#27). The culprit of the problem is in the assets URLs — I cannot decipher the actual file path by its URL. For example, /assets/application.css may refer to either app/assets/stylesheets/application.css, lib/assets/stylesheets/application.css, or vendor/assets/stylesheets/application.css.

I wonder, how do I change assets URLs to one of the following?

  • /app/assets/stylesheets/application.css (matches actual file path, perfect solution)
  • /assets/application.css?source_url=app/assets/stylesheets/application.css (introduces source_url query parameter)
@josh
Copy link
Contributor

josh commented Mar 22, 2012

I think we'll handle this with Source Maps.

@josh josh closed this as completed Mar 22, 2012
@NV
Copy link
Author

NV commented Mar 22, 2012

I don’t think we will since files transformed by Source Maps cannot be edited.

@josh
Copy link
Contributor

josh commented Mar 22, 2012

They will have pointers to the source files.

@NV
Copy link
Author

NV commented Mar 22, 2012

They do, but in my case it doesn’t help at all since all resources become unable to edit in Chrome DevTools.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants