This repository was archived by the owner on Sep 6, 2021. It is now read-only.
Fix for: Reload With(out) Extensions not working#15017
Merged
narayani28 merged 1 commit intoadobe:masterfrom Feb 12, 2020
Merged
Fix for: Reload With(out) Extensions not working#15017narayani28 merged 1 commit intoadobe:masterfrom
Reload With(out) Extensions not working#15017narayani28 merged 1 commit intoadobe:masterfrom
Conversation
In Brackets 1.14.1 a browser reload failed (menu items Debug | Reload With(out) Extensions). Rejecting the `_disableCache()` promise when no remote debugging port is found, will fix this.
niteskum
pushed a commit
that referenced
this pull request
Mar 25, 2020
Fix for: `Reload With(out) Extensions` not working
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In Brackets 1.14.1 a browser reload fails (menu items Debug | Reload With(out) Extensions will do completely nothing at the moment).
Rejecting the
_disableCache()promise when no remote debugging port is found, will fix this.