-
Notifications
You must be signed in to change notification settings - Fork 45
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
[#702] Improve mirroring summary #1122
Conversation
e994014
to
062d8a1
Compare
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.
LGTM, but please merge after rmt 2.16 is released
71e0615
to
be401e6
Compare
be401e6
to
df5fd7b
Compare
How should I update |
Just merged master and updated the release to version 2.17 |
Description
This PR was created to make easier the implementation of the previous one as there were many conflicts by merging the debian changes that refactored the classes used by the implementation of this feature.
These are the changes I did on my technical interview to improve the summary of the mirroring process.
Fixes #702
Other Notes
Maybe we can update some rubocop rules
Regarding
spec/lib/rmt/cli/mirror_spec.rb
:RSpec/ExpectOutput: Use expect { ... }.to output(...).to_stdout instead of mutating $stdout.
I was unable to test well the summary output with the
output
helper, so I decided to use the$stdout
which makes our test more robust.RSpec/MultipleExpectations
andRSpec/ExampleLength
were ignored because of the changes belonging to the summary output which have more information.RSpec/ClassLength
in this case there 3 more lines than the limit which is 177. Is there a reason for this number?I prefer deep modules (with a simple interface) than shallow modules (with a complex interface) as I learned from: A Philosophy of Software Design by John Ousterhout.