-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
Improve comments #26
Improve comments #26
Conversation
Codecov Report
@@ Coverage Diff @@
## master #26 +/- ##
=======================================
Coverage 89.34% 89.34%
=======================================
Files 6 6
Lines 807 807
=======================================
Hits 721 721
Misses 68 68
Partials 18 18 |
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.
@fsmiamoto
Thanks for the great work! I'm not a native English speaker, so this kind of PR is very helpful.
I commented just one point, can you check it?
fuzzyfinder.go
Outdated
@@ -604,16 +604,16 @@ func (f *finder) find(slice interface{}, itemFunc func(i int) string, opts []Opt | |||
} | |||
} | |||
|
|||
// Find displays a UI that provides fuzzy finding against to the passed slice. | |||
// The argument slice must be a slice type. If it is not a slice, Find returns | |||
// Find displays an UI that provides fuzzy finding against the provided slice. |
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.
an UI
Should we use a
instead of an
?
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.
Good catch!
I didn't put much thought to it, but looks like a
is the way to go here.
@ktr0731 |
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.
@fsmiamoto
LGTM. Thanks for your contribution!
While reading the source code, I saw the opportunity to improve some of the comments to make them clearer and fix some typos.
Let me know what you think and thanks for the awesome project.