Currently checker names redundantly "carry" the namespace when someone is navigating the tree. E.g. in the core folder you have core.DivisionByZero. The core. from the latter one should be removed, as I already know from the parent "folder" which category this checker belongs to – redundancy juts bloats the interface. (This, of course, applies to checkers with multiple parents in the hierarchy.)
Also, the plugin seems only to consider . (dot) as the hierarchical separator while some checkers use - (hyphen).
Is this a lack of guideline in CodeChecker, @dkrupp?
Currently checker names redundantly "carry" the namespace when someone is navigating the tree. E.g. in the
corefolder you havecore.DivisionByZero. Thecore.from the latter one should be removed, as I already know from the parent "folder" which category this checker belongs to – redundancy juts bloats the interface. (This, of course, applies to checkers with multiple parents in the hierarchy.)Also, the plugin seems only to consider
.(dot) as the hierarchical separator while some checkers use-(hyphen). Is this a lack of guideline in CodeChecker, @dkrupp?