Report a [[platform]] entry without a name in Scan.toml
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
Research direction
Start from the Scan.toml parsing of the [[platform]] table and the code added by #215 that already reports a non-string name or path at its position; mirror that path for the missing/empty name case, including the source position. Reproduce first with the nmae typo from the issue and run bal scan --platforms=sonarqube, then a plain bal scan, to see both silent outcomes. Done means an entry without a usable name is reported with its position instead of being skipped, and the existing #215 tests still pass.
Written by the indexing model from the issue text.
Description
Area
Configuration
Description
A [[platform]] entry in Scan.toml with no name, or an empty one, is skipped without a message, although the docs say both name and path are required. With a typo such as nmae = "sonarqube", bal scan --platforms=sonarqube fails with "platform 'sonarqube' is not available; add its plugin to the [[platform]] table of Scan.toml", which points the user at an entry that already exists.
Raised in the review of #215 (comment) and left out of the 0.14.0 / 0.11.2 release-readiness fixes. #215 already reports a non-string name or path as an error at its position; a missing or empty name is the remaining silent case.
Steps to Reproduce
-
In a package, add this
Scan.toml:[[platform]] nmae = "sonarqube" path = "plugin.jar" -
Run
bal scan --platforms=sonarqube.
Expected Behavior
The entry without a name is reported with its position. Whether it is an error (exit 1) or a warning is to be decided.
Actual Output
bal scan: error: platform 'sonarqube' is not available; add its plugin to the [[platform]] table of Scan.toml. A plain bal scan ignores the entry silently.
Scan Tool Version
0.14.0 (with #215)
- Dominant language
- Java
- Stars
- 15
- Forks
- 12
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 29
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ballerina-platform/static-code-analysis-tool
-
Use the released ballerina/scan 1.0.0 on the 0.11.x linePossibly taken A pull request linked to this issue is open or already merged. OpenArea/Build Type/Task
Difficulty 1/5 Under an hour Newbie friendliness 72/100
ballerina-platform/static-code-analysis-tool#200 · 1 comment ·
Maintainers usually reply within 1 day
-
Clarify the breaking location change and the password placeholder exception in the 0.14.0 changelogPossibly taken A pull request linked to this issue is open or already merged. OpenType/Docs
Difficulty 1/5 1-3 hours Newbie friendliness 74/100
ballerina-platform/static-code-analysis-tool#198 · 2 comments ·
Maintainers usually reply within 1 day
-
Area/CLI Type/Improvement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ballerina-platform/static-code-analysis-tool#140 ·
Maintainers usually reply within 1 day
-
Area/Configuration Type/New Feature
Difficulty 3/5 1-2 days Newbie friendliness 52/100
ballerina-platform/static-code-analysis-tool#211 ·
Maintainers usually reply within 1 day
-
ballerina:2 reports methods of an object constructor that initializes a typed class fieldPossibly taken @TharmiganK claimed this 2 days ago. OpenArea/Rules Type/Bug
Difficulty 3/5 1-2 days Newbie friendliness 22/100
ballerina-platform/static-code-analysis-tool#201 · 1 comment ·
Maintainers usually reply within 1 day
All issues in ballerina-platform/static-code-analysis-tool
Similar issues
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
xerial/sqlite-jdbc#1515 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
eclipse-dirigible/dirigible#8636 · 1 comment ·
Maintainers usually reply within 1 day
-
bug severity-medium XS
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
nikolas-charalambidis/facepalm-maven-plugin#291 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
OakLoaf/PluginUpdater#264 ·
Maintainers usually reply within 1 day
-
[Bug]: withStartupTimeout() changes the startup timeout of all containers that use the default wait strategyPossibly taken @aymenjamaaoui claimed this today. Opentype/bug
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
testcontainers/testcontainers-java#12171 ·
Maintainers usually reply within 1 day