Skip to content

fix: keep Gradle map-style dependencies in vg scan - #682

Open
vibgrate-team wants to merge 1 commit into
mainfrom
cursor/gradle-map-dependencies-ceb2
Open

vibgrate-team wants to merge 1 commit into
mainfrom
cursor/gradle-map-dependencies-ceb2

Conversation

@vibgrate-team

Copy link
Copy Markdown
Contributor

Keeps Gradle map-style dependency declarations in vg scan instead of dropping them.

What changed

  • parseGradleBuild now reads Groovy group: 'x', name: 'y', version: 'z' and Kotlin group = "x", name = "y", version = "z" maps, with or without parentheses and in any key order.
  • Each map goes through the same coordinate path as string notation, so configuration names, section rules and de-duplication are unchanged.
  • A map without a version key is treated like a string coordinate without a version.

Tests

pnpm test, pnpm lint and pnpm typecheck pass.

Closes #661

Groovy group/name/version maps and the Kotlin key = "value" form were
ignored, so those dependencies never showed up in vg scan or vg sbom
export. Read both forms in any key order, with or without parentheses,
and pass the coordinate through pushGradleCoord so configuration
sections and de-duplication match string notation.

Signed-off-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: ABIZ - Agentic Business Record Standard <ops@to.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: Gradle map-style dependencies (implementation group: 'g', name: 'a', version: 'v') are dropped

2 participants