Add support for simple Gradle version catalog aliases

Aberta
#4 0 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
62/100
Tipo de issue
Funcionalidade
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
java, python

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Python
Estrelas
2
Forks
1
Merge médio
1h 22min
PRs com merge (30d)
2

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de ayushdoesdev/verspect

Todas as issues de ayushdoesdev/verspect

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.