[feat] Adding report annotation for json export #4380
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
It is an additional feature for parseing to have report annotation fields when the user wants to export the results to json.
cservakt
added
usability 👍
bruntib
approved these changes
Nov 11, 2024
There was a problem hiding this comment.
The JSON output of CodeChecker parse has a version attribute which is currently 1. In what situations should we increase this number? I think, the extension of the current format, like adding annotations is not harmful, but maybe we should discuss this question sometime.
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.
It is an additional feature for parseing to have report annotation fields when the user wants to export the results to json.