Fix line coverage in html

[gayaldassanayake]

Purpose

Fixes #29

Approach

1. Mark all lines in the HTML for a given issue [start, end]
2. For rule 3,4,5,6, set the public keyword as the location. That way only the definition line of the class/object/method/function is colored.

It looks as follows now.

Check List

• Read the Contributing Guide
• Added necessary tests
  • Unit Tests
  • Integration Tests

[Copilot]

Pull Request Overview

This PR enhances HTML line highlighting to cover full issue ranges, adjusts issue reporting to pinpoint the visibility token, and bumps version identifiers.

• Highlight all lines between an issue’s start and end in SingleFileContent.jsx instead of a single line.
• Report issues at the exact visibility token in StaticCodeAnalyzer.java and update related tests for rules 3–6.
• Bump project versions to 0.9.1-SNAPSHOT and update HTML report fixtures to reference the new bundle names.

Reviewed Changes

Copilot reviewed 13 out of 13 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
static-code-analysis-report/src/components/SingleFileContent.jsx	Iterate over full line ranges for each issue, with validation
static-code-analysis-report/src/main/java/io/ballerina/scan/internal/StaticCodeAnalyzer.java	Report issues at the public token and introduce getQualifier
scan-command/.../Rule003And004Test.java	Adjust expected line numbers to only the definition line
scan-command/.../Rule005And006Test.java	Adjust expected line numbers to only the definition line
static-code-analysis-report/package.json	Version bumped to 0.9.1-SNAPSHOT
scan-command/tool-scan/Dependencies.toml	Version bumped to 0.9.1-SNAPSHOT
scan-command/tool-scan/Ballerina.toml	Version bumped to 0.9.1-SNAPSHOT
scan-command/tool-scan/BalTool.toml	JAR path updated to 0.9.1-SNAPSHOT
scan-command/.../issues-html-report.txt (windows/unix/common)	Updated script filename hashes in fixtures

Comments suppressed due to low confidence (1)

static-code-analysis-report/src/components/SingleFileContent.jsx:10

• The new multi-line highlighting and the invalid-range error branch aren’t covered by existing tests. Consider adding unit tests for both happy-path and error-handling behaviors.

useEffect(() => {

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud