Add support for simple Gradle version catalog aliases

Offen
  • Stimmt etwas nicht?
#4 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
62/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
java, python
Bereich
backend, documentation

Rechercherichtung

Start in backend/app/scanners/analyzers/java.py to see how literal group:artifact:version Gradle declarations are extracted, then check the fixtures in backend/tests/scanners/test_java_analyzer.py. The change should read gradle/libs.versions.toml as data, resolve simple [libraries] aliases for implementation, api and test configurations, and leave anything unsupported unresolved. Done means the new fixture tests pass alongside the existing literal-parsing tests, and docs/languages.md describes the added support and its limits.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

enhancement good first issue

Summary

Gradle analysis currently extracts literal group:artifact:version declarations. Simple Gradle version catalog aliases in gradle/libs.versions.toml are not resolved, so dependencies referenced as implementation(libs.alias) or equivalent are missing from the inventory.

Affected files

  • backend/app/scanners/analyzers/java.py
  • backend/tests/scanners/test_java_analyzer.py
  • docs/languages.md

Scope

Read the conventional gradle/libs.versions.toml catalog and resolve simple library aliases used by supported dependency configurations. Parse the TOML as data only; never execute Gradle scripts or fetch artifacts. Leave unsupported expressions unresolved.

Acceptance criteria

  • The scanner reads gradle/libs.versions.toml when present.
  • Simple [libraries] aliases resolve from inline versions and version.ref entries.
  • Basic implementation(libs.alias), api(libs.alias), and test-configuration references are recognized.
  • Existing literal Gradle dependency parsing remains unchanged.
  • Complex expressions, unsupported catalog features, and unresolved version references remain unresolved rather than guessed.
  • Fixture-based tests cover inline versions, version.ref, supported configurations, unresolved expressions, and literal parsing.
  • docs/languages.md accurately documents the added catalog support and remaining limitations.

Testing expectations

Run the focused Java analyzer tests and relevant backend scanner tests. Confirm documentation claims match tested behavior.

Vorherrschende Sprache
Python
Sterne
2
Forks
1
Ø Merge
1 Std. 22 Min.
Gemergte PRs (30 T.)
2

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus ayushdoesdev/verspect

Alle Issues in ayushdoesdev/verspect

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.