Improvement of Metadata handling in Report Converter #4600
Replies: 1 comment
-
|
Hi, Yes, the handling of metadata.json is a hot topic in our team recently, as we are also doing some development that is related to this file. The problem is that the concept of metadata.json doesn't exist currently on code-level as a class or something. The JSON structure is natively assembled and dumped to a file by the analyzer. To be precise, there is a class on server-side that could be used as a starting point: https://github.com/Ericsson/codechecker/blob/master/web/server/codechecker_server/metadata.py I would say that we should create a Thank you! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I am integrating currently codechecker with some inhouse analysis tools. There we use the workflow, that we generate reports in native formats and then use a patched version of the report converter, where we have implemented the AnalyzerResultsBase class. In the default way the possibilities to provide metadata alongside the converted files, i.e., via commandline of the converter is quite limited. As we have all relevant information in the reports we would like to make this directly from the conversion. (Of course, it can be implemented by providing the metadata.json from another tool and a dedicated call.)
This just requires minimal modifications to AnalyzerResultsBase, such that create metadata is called in any case and is beeing overwritable.
In general, is this an approach you consider as good? And if so, I would like to contribute these changes, are you interested in that?
Beta Was this translation helpful? Give feedback.
All reactions