How fri-day/sonar-gosu-plugin works
• Source Files -> Parser -> AST -> Rules Analysis -> SonarQube Issues
• Configuration Flow
• Metrics Collection Flow
• Report Generation Flow
Integration Points (Purple Diamonds)
• SonarQube API Integration
• ANTLR4 Integration
• Test Framework Integration
Key Subsystems
a. Measures Subsystem
• Code Metrics
• Complexity Calculations
• Test Coverage
b. Issues Subsystem
• Issue Collection
• Issue Reporting
• Suppression Handling
External Dependencies (Gray Rectangles)
• SonarQube Server
• ANTLR4 Runtime
• Gradle Build System
The plugin's architecture as a SonarQube extension
• Clear boundaries between plugin code and SonarQube platform
• Extension points (Sensor, Rules, Metrics)
The parsing pipeline
• Source Files -> ANTLR4 Lexer -> Tokens -> ANTLR4 Parser -> AST -> Rule Visitors
Rules organization
• Rules by category (bugs, vulnerabilities, code smells)
• Relationship to quality profiles
Metrics collection
• Code size metrics
• Complexity metrics
• Test metrics
Keep the abstraction level appropriate by:
• Focusing on major components rather than individual classes
• Showing primary data flows and interactions
• Highlighting extension points and integration boundaries
• Including key technical decisions (e.g., ANTLR4 usage)