Skip to content

SonarQube evidence uses A-vs-A snippet pairing instead of A-vs-B #7

@drogers0

Description

@drogers0

Summary

SonarQube findings construct compare evidence as A-vs-A instead of A-vs-B.

Affected code

  • src/clonehunter/engines/sonarqube_engine.py:35

Problem

CandidateMatch is built with the same snippet object for both sides:

  • snippet_a=snip
  • snippet_b=snip

This loses pairwise context and produces incorrect compare/diff payloads in reporters.

Expected

Build a snippet for side A and a snippet for side B so evidence reflects the actual duplication pair.

Impact

Incorrect evidence/compare output for SonarQube findings (JSON/HTML).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions