Add support for simple Gradle version catalog aliases

Ouverte
  • Quelque chose ne va pas ?
#4 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
62/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
Active
Stack technique
java, python
Domaine
backend, documentation

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Python
Étoiles
2
Forks
1
Merge moyen
1 h 22 min
PR mergées (30 j)
2

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de ayushdoesdev/verspect

Toutes les issues de ayushdoesdev/verspect

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.