Conversation
…dles caused by the new getChecksum
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #401 +/- ##
==========================================
+ Coverage 52.36% 52.53% +0.17%
==========================================
Files 37 38 +1
Lines 6065 6129 +64
Branches 648 654 +6
==========================================
+ Hits 3176 3220 +44
- Misses 2241 2255 +14
- Partials 648 654 +6 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
stschiff
left a comment
There was a problem hiding this comment.
Nice, looks great, from my perspective. Just to be clear: the new rectify only detects changed checksums, not missing ones. That's intended, right?
|
Yes - that's what I implemented. But I wasn't sure about this. My reasoning was that rectify should purely "make things right", and a package without checksums is valid. But now I'm wondering if it's more convenient in practical use to have it add the checksums. What do you think? |
|
I think it would be less surprising if this updates and also adds checksums in case they're missing. |
|
Yes - I agree now. #406 implements the relevant change. |
make rectify add checksums when they are not there yet
As decided in #343 I renamed
rectifytomodifyand then built a newrectifythat simply searches for packages with changed checksums to automatically fix them. This is a breaking change, of course. This PR also includes new dependencies that speed up the MD5 sum computation considerably.Remaining TODOs are:
Add a warning or generally better command line output tomodifyto highlight that it changes all input packages.Add some golden tests forrectify.