Cargo publish should warn/error on unknown settings in Cargo.toml #3576
Labels
A-diagnostics
Area: Error and warning messages generated by Cargo itself.
A-manifest
Area: Cargo.toml issues
S-needs-design
Status: Needs someone to work further on the design for the feature or fix. NOT YET accepted.
I recently tried to publish both category and badge information for some of my crates. I couldn't figure out why this information wasn't being displayed on crates.io, and eventually I figured out that I was using an old version of
cargo
. Ifcargo
warned on values that it didn't understand when running publish I think this could have been avoided. I'm not certain if very many people put custom things in their Cargo.toml and some crates use that, but I think in general it'd be good to have thepackage
namespace locked down like that. This wouldn't have caught the problem with the newbadges
namespace, but that might cause too many false positives.What infrastructure is proposed to resolve this probably overlaps with #2489.
The text was updated successfully, but these errors were encountered: