-
-
Notifications
You must be signed in to change notification settings - Fork 320
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Swap dirs-next
dependency to cargo-team maintained home
crate
#1207
Conversation
Signed-off-by: Utkarsh Gupta <utkarshgupta137@gmail.com>
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #1207 +/- ##
==========================================
+ Coverage 73.16% 73.18% +0.01%
==========================================
Files 75 75
Lines 6030 6030
==========================================
+ Hits 4412 4413 +1
+ Misses 1618 1617 -1
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The argument makes sense but this is also a pretty tiny impact one way or another.
From some digging, the current* windows home folder goes to |
So... client-go uses this implementation favouring IOW this doesn't change anything significant for us, and both answers are correct; it's client-go that is wrong 🙃 Going to merge this just because it's cargo maintained. This crate has already swapped once and there's only 2 people in the org that maintains the dirs-next. The long, historical thread on rust is probably one of the better sources of what's going on here with all these small lib crates: rust-lang/rust#71684 |
home
cratedirs-next
dependency to cargo-team maintained home
crate
To bring some extra fun, the original |
Motivation
dirs
is an unnecessarily big dependency for a single functionSolution
Use the smaller, cargo-team maintained
home
crate