where the resource_attribute represents a file-viewexample, where every file has license detection issues potentially, and the
codebase_attribute is an issue-viewexample, where we go through issues (unique issues, with all their occurances) one by one, instead of files.
The issue-view makes more sense in terms of review and resolving, and as @pombredanne suggests even dropping the resource_attribute entirely, and just have the codebase_attribute as an issue-view, makes sense.
Presently with https://github.com/nexB/scancode-results-analyzer/pull/44, there are two attributes added,
where the
resource_attribute
represents afile-view
example, where every file has license detection issues potentially, and thecodebase_attribute
is anissue-view
example, where we go through issues (unique issues, with all their occurances) one by one, instead of files.The
issue-view
makes more sense in terms of review and resolving, and as @pombredanne suggests even dropping theresource_attribute
entirely, and just have thecodebase_attribute
as anissue-view
, makes sense.