-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Include public/private dependency status in cargo metadata
#14502
Labels
C-feature-request
Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`
Command-metadata
S-accepted
Status: Issue or feature is accepted, and has a team member available to help mentor or review
Z-public-dependency
Nightly: public-dependency
Comments
This seems like basic enough of metadata for us to include. |
@rustbot claim |
eopb
added a commit
to eopb/cargo
that referenced
this issue
Sep 6, 2024
eopb
added a commit
to eopb/cargo
that referenced
this issue
Sep 6, 2024
eopb
added a commit
to eopb/cargo
that referenced
this issue
Sep 6, 2024
eopb
added a commit
to eopb/cargo
that referenced
this issue
Sep 6, 2024
eopb
added a commit
to eopb/cargo
that referenced
this issue
Sep 6, 2024
fixes rust-lang#14502 This change introduces a new method, `Dependency::serialized` which replaces the direct `Serialize` implmentation on `Dependency`. This matches the pattern used by `Package` with its `Package::serialized`, and enables us to influence the serialization format with unstable flags. I replaced borrowed types in `SerializedDependency` with owned variants to satisfy the borrow checker. This shouldn't be an issue since `Dependency` is cheap to copy.
eopb
added a commit
to eopb/cargo
that referenced
this issue
Sep 6, 2024
fixes rust-lang#14502 This change introduces a new method, `Dependency::serialized` which replaces the direct `Serialize` implementation on `Dependency`. This matches the pattern used by `Package` with its `Package::serialized`, and enables us to influence the serialization format with unstable flags. I replaced borrowed types in `SerializedDependency` with owned variants to satisfy the borrow checker. This shouldn't be an issue since `Dependency` is cheap to copy.
eopb
added a commit
to eopb/cargo
that referenced
this issue
Sep 6, 2024
fixes rust-lang#14502 This change introduces a new method, `Dependency::serialized` which replaces the direct `Serialize` implementation on `Dependency`. This matches the pattern used by `Package` with its `Package::serialized`, and enables us to influence the serialization format with unstable flags. I replaced borrowed types in `SerializedDependency` with owned variants to satisfy the borrow checker. This matches `SerializedPackage` and shouldn't be an issue since `Dependency` is cheap to copy.
27 tasks
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Labels
C-feature-request
Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`
Command-metadata
S-accepted
Status: Issue or feature is accepted, and has a team member available to help mentor or review
Z-public-dependency
Nightly: public-dependency
Problem
related to rust-lang/rust#44663
Information about whether or not a dependency is public is not included in the output of
cargo metadata
.This could be useful for custom subcommands.
cargo override
, would find this useful for eopb/cargo-override#121Proposed Solution
When
-Zpublic-dependency
is enabled, include a boolean flag incargo metadata
s output atpackages[].dependencies[].public
.If
-Zpublic-dependency
is not enabled, this flag should not appear incargo metadata
output.Notes
If this feature request is accepted, I'm happy to claim and take a crack at working on it
The text was updated successfully, but these errors were encountered: