Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .github/workflows/sonarqube.yml
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,11 @@ jobs:
- uses: actions/checkout@v6
with:
fetch-depth: 0 # Shallow clones should be disabled for a better relevancy of analysis
- uses: actions/setup-node@v6
with:
node-version-file: '.tool-versions'
cache: 'npm'
- run: npm ci
- uses: SonarSource/sonarqube-scan-action@v7
env:
SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
Expand Down
1 change: 1 addition & 0 deletions sonar-project.properties
Original file line number Diff line number Diff line change
@@ -1 +1,2 @@
sonar.projectKey=abtion_adonisjs-template_e6981c04-79a9-46d2-9b70-6706c53d1f55
sonar.typescript.tsconfigPaths=tsconfig.json,inertia/tsconfig.json

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Explicitly defining sonar.typescript.tsconfigPaths addresses the resolution issue for Sonar, but there is an underlying inconsistency in the project configuration. The root tsconfig.json (line 8) references ./tsconfig.inertia.json, yet the actual file is located at inertia/tsconfig.json.

By correcting the reference in the root tsconfig.json to point to ./inertia/tsconfig.json, Sonar (and the TypeScript compiler) would be able to resolve the entire project structure naturally. This would also allow you to simplify the Sonar configuration to just the root config, avoiding potential double-analysis or metric inflation that can occur when overlapping configurations are listed explicitly.

Loading