-
Notifications
You must be signed in to change notification settings - Fork 53
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
feat: add firstMatch option for findNvim #397
Conversation
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.
LGTM after naming nit. Thanks!
Future improvement would be to add Windows paths. And to allow the caller to pass specific paths (both directories and files) to search.
Problem: Code coverage is not counted for Windows. For example, in #397 codecov flags the `if (LOCALAPPDATA)` branches. Solution: Run codecov on all platforms (but only for a single node version, to be frugal).
The codecov complaints about the Windows codepaths, should be fixed after #398 |
Problem: Code coverage is not counted for Windows. For example, in #397 codecov flags the `if (LOCALAPPDATA)` branches. Solution: Run codecov on all platforms (but only for a single node version, to be frugal).
@justinmk Thanks for your patient review! This is my first time contributing to node-client, and I'm so excited. |
It's great to have some help around here :) |
Closes #370 and #267
Introducing a new 'stopOnFirstMatch' option for the findNvim function, which helps reduce the number of system calls when the caller only need one valid match. Additionally, the search now includes common locations where Neovim might be installed.