Fix incorrect assert() handling #10
Merged
Conversation
This file contains 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
Fixes tomblind#74 by starting the trace one level deeper, skipping over `debuggerAssert` as was likely intended.
|
Thank you guys for supporting the extension, I already forgot that I opened some issue (and I used the unpatched version for a long time >.<). It is sad that the original author has no activity, I hope he's okay. I actively use this extension for my work, but only basic functionality. I will be happy to try new version. |
|
Looks good to me. I also have tested this locally. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes tomblind#74 by starting the trace one level deeper, skipping over
debuggerAssertas was likely intended. This is the fix suggested by @TIMONz1535 in the issue on the original repo.