-
Notifications
You must be signed in to change notification settings - Fork 223
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
lib/Rex/Config.pm: slurp file content using IO::File. #1511
base: master
Are you sure you want to change the base?
Conversation
73badfc
to
a93c45b
Compare
Thanks @monsieurp for your contribution! Tis PR is still marked as draft only, but reading through the linked issue and the proposed changes, I can provide some early feedback below and/or as code comments.
Hmm, yeah, I agree it's probably fine to skip changelog entries for changes such as automated code formatting, refactoring, or CI workflow changes.
As a minimum quality requirement the current test suite should still pass. Ideally, if a changed code path is not covered yet, tests could be added first (to demonstrate a code is solid either by fixing a failing test to proving that it still passes the tests). Currently There are currently 35 instances of I've fixed some CI-related issues recently, so you might need to rebase this PR on top if current default branch, and (force) push your branch again. |
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.
Let's make sure all tests pass. Please rebase these changes on top of the default branch in order to test them against the current state.
my @lines = do { | ||
use IO::File; | ||
my $fh = IO::File->new( $config_file, 'r' ); | ||
join '', $fh->getlines(); |
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.
Can it be that t/config-ssh.t
fails because now all lines of the file is concatenated with join
while it was treated as an array of lines before?
ps.: a git commit is explicit about which files are being changed, so there's no need to duplicate that info in the commit message. and to stop it with the period. Also do not end the subject line with a period. E.g. instead of:
it's fine to simply write:
It might also work better to explain what and why vs. how. E.g.
|
a93c45b
to
eb6a7bb
Compare
eb6a7bb
to
fc59cb9
Compare
fc59cb9
to
037b3bb
Compare
Fixes #1466.
This PR is an attempt to fix #1466. The ticket is self-explanatory as well as those changes.
Checklist