Stacktraces in comments should be escaped #609 #638
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
…ents-should-be-escaped
EgorkaKulikov
approved these changes
Aug 2, 2022
Vassiliy-Kudryashov
deleted the
Vassiliy-Kudryashov/609-stackstraces-in-comments-should-be-escaped
branch
tamarinvs19
pushed a commit
that referenced
this pull request
Aug 4, 2022
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.
Description
Warning line is being escaped (namely, symbols \b \n \t \r)
Fixes #609
Type of Change
How Has This Been Tested?
Manual Scenario
See an example in the issue, test generation shouldn't fail anymore
Checklist (remove irrelevant options):