Similar to #247 but for Cargo.toml manifests instead of Cargo.lock
Description of changes:
Mask only dependencies that are local, i.e. have path set. If they do not have this field set, they should be pulled from some registry.
This is not completely bulletproof as a local dependency could theoretically also point to a package outside a workspace which would have the same name as a package in the workspace, but this scenario is somewhat unlikely.
LukeMathWalker
commented
5 months ago
Issue #, if available:
Fixes #224
Similar to #247 but for
Cargo.tomlmanifests instead ofCargo.lockDescription of changes:
Mask only dependencies that are local, i.e. have
pathset. If they do not have this field set, they should be pulled from some registry.This is not completely bulletproof as a local dependency could theoretically also point to a package outside a workspace which would have the same name as a package in the workspace, but this scenario is somewhat unlikely.