Skip to content
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

Merged
merged 2 commits into from
Sep 8, 2020
Merged

Improve comments #26

merged 2 commits into from
Sep 8, 2020

Conversation

fsmiamoto
Copy link
Contributor

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.

@codecov
Copy link

codecov bot commented Sep 7, 2020

Codecov Report

Merging #26 into master will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #26   +/-   ##
=======================================
  Coverage   89.34%   89.34%           
=======================================
  Files           6        6           
  Lines         807      807           
=======================================
  Hits          721      721           
  Misses         68       68           
  Partials       18       18           

Copy link
Owner

@ktr0731 ktr0731 left a 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.
Copy link
Owner

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?

Copy link
Contributor Author

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.

@fsmiamoto
Copy link
Contributor Author

@ktr0731
Great!
Happy to help improve things.

Copy link
Owner

@ktr0731 ktr0731 left a 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!

@ktr0731 ktr0731 merged commit 66a4a15 into ktr0731:master Sep 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants