Consider using cargo-util-schemas instead of cargo_toml
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 12k
- Forks
- 332
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 17
Description
Summary 💡
As suggested in a Fedora package review, you might consider replacing the cargo_toml crate with cargo-util-schemas (plus toml). While cargo-util-schemas doesn’t have as much high-level functionality as cargo_toml, it seems like it should be adequate for what onefetch-manifest needs.
Motivation 🔦
The advantage of cargo-util-schemas is that it is the official implementation of serialization and deserialization schemas used by cargo itself, so if you use it, you can be confident that your Cargo.toml support remains consistent with cargo‘s.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting how onefetch-manifest currently uses the cargo_toml crate, then compare those needs with the cargo-util-schemas and toml crates. Done means Cargo.toml serialization and deserialization remain supported consistently with cargo after the dependency replacement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100