Add DisableHash setting to ease debugging javascript with Chrome #375
Conversation
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
|
Hi, Nobody else want this feature ? It was already implemented ? Thx, |
|
I just started using cassette and noticed the same issue with losing breakpoints. What ever happened to this PR? |
…o the file name during debug. Javascript break points were being lost in Chrome every time the file changed because Chrome uses the entire path for applying saved break points.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Javascript break points were being lost in Chrome every time the file changed because Chrome uses the entire path for applying saved break points.
This change adds a configuration setting to allow the file hash to not be added to the asset file names during debug.