-
Notifications
You must be signed in to change notification settings - Fork 85
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
Code formatting and documentation #149
Code formatting and documentation #149
Conversation
I used cargo fmt with default settings, as it's good quality and pretty standard. That should make code easier to read, and more uniform. This also adds some consistency on EOF newlines. I manually reviewed all changes.
I think that's about all i can clean up and document. |
src/ignore/git.rs
Outdated
assert_eq!(filter.only_dir, true); | ||
assert_eq!(filter.negate, false); | ||
assert!(filter.only_dir); | ||
assert!(filter.negate); |
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.
Looks like this assertion is the opposite from the original one. Haven't that affected the tests at all?
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.
It sure did. I ran cargo test
on linux, so i didn't catch that since it's a windows test 😓
I was waiting to see the workflow results for the windows tests to see if i hadn't screwed anything up there
Hooray! Great job, really! Thank you so much. Merged with a deep feeling of satisfaction :) |
This PR aims to make the code easier to work on by formatting the code with
cargo fmt
, refactoring and cleaning up some of the code, and adding comments to document the code.For the formatting, i manually went through and verified every change.
I kept the formatting commit separate on purpose, so if you don't like it i can rebase the PR without them.