Promote common dependencies to workspace level
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.6k
- Forks
- 1.3k
- Avg merge
- 8h 47m
- Merged PRs (30d)
- 19
Description
Description
Promote commonly occuring dependencies to workspace level.
Motivation
This can potentially make dependency management easier.
Current Implementation
tracing, futures, tokio are all over the place.
Are you planning to do it yourself in a pull request ?
Yes
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
Inspect the workspace dependency declarations and search for the occurrences of tracing, futures, and tokio across the repository. Determine which dependencies are common enough to promote and verify that the workspace remains consistent after centralizing them. Done means common dependency management is simplified without changing crate behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100