Reload Brackets, changes to extensions are cached (& unit tests) #1551

Closed
jrowny opened this Issue Sep 5, 2012 · 7 comments

5 participants

@jrowny

With the new brackets shell changes to extensions are cached and therefore don't reload when you hit F5 or reload brackets. To demonstrate the issue:

  1. Add alert("I am here"); to brackets.js just after the define
  2. hit f5, it works fine
  3. add the same code to an extension in the user directory, and hit f5
  4. nothing :(
  5. unless brackets is completely closed and re-opened

Kinda a pain if you're working on an extension and just want to hit f5 to see your change.

@peterflynn
Adobe Systems Incorporated member

Possibly same bug as adobe/brackets-shell#32

@jasonsanjose jasonsanjose was assigned Sep 11, 2012
@pthiess
Adobe Systems Incorporated member

Reviewed - assigned to @jasonsanjose

@jasonsanjose
Adobe Systems Incorporated member

I'll update here with a comment and update the developer docs on how to disable the cache.

@jasonsanjose
Adobe Systems Incorporated member
  1. Choose "Debug > Show Developer Tools" in Brackets-Shell
  2. In the developer tools tab that launches in Chrome, click the gear icon in the lower right
  3. Check "Disable cache" in the "General" tab
@peterflynn
Adobe Systems Incorporated member

Note: this issue still occurs for unit test spec files too ("*-test.js"). Same workaround applies.

@peterflynn
Adobe Systems Incorporated member

Also note: the workaround only works while the Developer Tools window is open. If you close it, the bug comes back for any further changes to extension/spec code.

Ideally, we should figure out a way for brackets-shell to just automatically do whatever the "Disable cache" checkbox does (or maybe it could even be done in brackets core code, by pinging our own remote debugging URL?).

@njx
Adobe Systems Incorporated member

I think this is now being tracked by #1744. Closing.

@njx njx closed this Nov 10, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment