Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[7.5.0] Include apparent names of deps in bazel mod JSON output #24678

Closed
bazel-io opened this issue Dec 13, 2024 · 2 comments
Closed

[7.5.0] Include apparent names of deps in bazel mod JSON output #24678

bazel-io opened this issue Dec 13, 2024 · 2 comments
Milestone
7.5.0 release blo...

Comments

@bazel-io
Copy link
Member

Forked from #23787
@bazel-io bazel-io added this to the 7.5.0 release blockers milestone Dec 13, 2024
@bazel-io
Copy link
Member Author

Cherry-pick was attempted but there were merge conflicts in the following file(s). Please resolve manually.

src/main/java/com/google/devtools/build/lib/bazel/bzlmod/BazelModuleInspectorValue.java
src/main/java/com/google/devtools/build/lib/bazel/bzlmod/modcommand/JsonOutputFormatter.java

cc: @bazelbuild/triage

@iancha1992
Copy link
Member

Cherry-pick was attempted but there were merge conflicts in the following file(s). Please resolve manually.

src/main/java/com/google/devtools/build/lib/bazel/bzlmod/BazelModuleInspectorValue.java src/main/java/com/google/devtools/build/lib/bazel/bzlmod/modcommand/JsonOutputFormatter.java

cc: @bazelbuild/triage

cc: @fmeum @Wyverald @meteorcloudy

fmeum added a commit to fmeum/bazel that referenced this issue Jan 7, 2025
@fmeum
[7.5.0] Include apparent names of deps in bazel mod JSON output
bda20d1 
This allows IDEs to query for the direct dependencies of the root module as well as how they can refer to them from the point of view of the root module.

Also always emit `name` and `version` so that consumers don't have to know how to parse module keys.

Work towards bazelbuild#22691

Closes bazelbuild#23787.

PiperOrigin-RevId: 693453084
Change-Id: Ie3fd5e89301d8e83d0eaa686188634923853f01a
(cherry picked from commit 1003d2c)

Fixes bazelbuild#24678
@fmeum fmeum mentioned this issue Jan 7, 2025
Merged
meteorcloudy pushed a commit that referenced this issue Jan 9, 2025
@fmeum
[7.5.0] Include apparent names of deps in bazel mod JSON output (#2…
74d3d1b 
…4847)

This allows IDEs to query for the direct dependencies of the root module
as well as how they can refer to them from the point of view of the root
module.

Also always emit `name` and `version` so that consumers don't have to
know how to parse module keys.

Work towards #22691

Closes #23787.

PiperOrigin-RevId: 693453084
Change-Id: Ie3fd5e89301d8e83d0eaa686188634923853f01a (cherry picked from
commit 1003d2c)

Fixes #24678
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
7.5.0 release blockers
Development

No branches or pull requests
2 participants
@bazel-io @iancha1992