cservakt
cservakt
> I'm a big fan of hard errors in favour of warnings. CodeChecker has a lot of output, and these warnings are hard to miss. Also, if I explicitly request...
> I don't intend to die on this hill, but I'm not yet convinced that a soft warning is the way to go. Breaking existing functionality is never a step...
> We definitely can't land this without tests. > > Also, I saw the following blame info from a tinyxml2 analysis in json format: > > ```json > "blameInfo": {...
> distinguish Thank you for the suggestion. I also thought about it to use None as default for args.
The ticket can be divided into the following tasks: 1. Implementing new converter type for metrics - Generate file-level aggregated metric results on the client side by an external tool...
Here is the new API endpoint structure:
The metric related table structure will look like this: