ansi syntax for message and trace #2949
Merged
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
Contributor
|
Is this really a good idea? Category matching regular expressions won't work very well with such status messages, so maybe it's better to clean up the jsons (strip ansi) from Allure framework reporter before generating the HTML report. |
Member
|
@noomorph, good catch. We can match categories against cleared messages & traces |
c2aecfb to
79e1a1a
Compare
baev
requested changes
Apr 18, 2025
baev
approved these changes
Apr 22, 2025
Member
1 task
Member
|
@todti good job! |
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.
Context
Added convert ansi syntax for error message and trace
Checklist