read cargo configs with/without .toml extension + make public API clearer #437
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The goal for my series of commits is to consolidate repeated functionality and make this crate easier to use for those using it's public Rust API.
commit ff1e158:
cargo_edit::registry::cargo_home
from unnecessarily getting $HOME, or checking UTF8 compliance.commit 03f6d74: introduce new structs to drive a new public, programmable API
.cargo/config
and.cargo/config.toml
filesRegistryReq
andRegistryIndex
structs, and attaches many of the freestanding functions incargo_edit::registry
into those.RegistryReq
notably allows a new user of the public API to more easily figure out the latest dependency of a crate without supplying a project directory.commit 1c986a6:
RegistryReq
andRegistryIndex
structscommit 933ebfe:
I plan to do a major bump once I am done editing the public API, if that is welcomed :)