-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
Increase test coverage for --sniffs
and --exclude
options
#474
Increase test coverage for --sniffs
and --exclude
options
#474
Conversation
89f3673
to
6bba777
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.
@fredden Thank you for this PR. Really happy to see tests for this part of the code base being added.
I've gone through the file with a fine toothcomb and left a number of nitpick comments, but also some functional questions.
Hope this helps for the next iteration.
…fig.sniffs-exclude
@jrfnl, I think this is ready for another review now. When we're happier with the final delta, I can rewrite the history so there are fewer commits before this is merged in. |
Now that we have tests asserting the result of these arguments and not just validation of their input.
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.
@fredden Thanks for the updates, looking much better!
The @return array<...>
tags are outdated now you've added the test names, so they need an update again.
Other than that, just one remark to go and this is ready for merge.
Co-authored-by: Juliette <[email protected]>
Co-authored-by: Juliette <[email protected]>
Co-authored-by: Juliette <[email protected]>
Fixes copy/paste error Co-authored-by: Juliette <[email protected]>
This reverts commit a0b31d9.
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.
@fredden Thanks for your work on this Dan! All good now as far as I'm concerned.
Re: your remark about tidying up the branch- what did you have in mind ? I could squash-merge the PR, unless you have a reason why you'd prefer otherwise ?
🎉 Yes. A squash-merge via GitHub is fine with me. |
Description
While working on #344, it was noted that there are no existing tests for the code being changed. This pull request aims to add some tests to cover the existing behaviour.
Suggested changelog entry
Related issues/external references
Related to #344
Types of changes
PR checklist