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
fix(is-ignored): allow paths ending with / #1453
fix(is-ignored): allow paths ending with / #1453
Conversation
Please fix lint errors, there is no reason to wrap the expression in extra parentheses. It's only needed if you call a method on return value but here you have expect(await x).toBe() and await is in double parentheses. |
Fixed the linting issues but the tests are still failing. Looking into it. |
What about if you just add |
🎉 This PR is included in version 1.10.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Oh that's a wonderful enhancement! Thank you ❤️ |
It makes me so happy to see folk contributing and @isomorphic-git-bot taking care of publishing... there's still things I wish were easier (running the tests and build still requires node 10 🤪 which is awfully out-of-date... something something experimental ECMAScript Modules stuff changed) but I tried to automate as much as I could. I never quite figured out how to make the repo auto-governed by an decentralized leaderless collective... |
Love the work you put in this project @wmhilton (and the rest of the folks hanging around here @jcubic). It's really cool to see a PR merged and be able to instantly use it! 💪 |
I second the sentiment shared by @SamVerschueren! |
Yes, the CI/CD is great in this repo thanks to @wmhilton that build the thing, even if some parts of it are out of date. |
* fix(is-ignored): allow paths ending with / * fix: linting errors * fix: fix tests
When using the
isIgnored
API, I noticed that providingdir/
asfilepath
argument didn't work and throws an errorpath must not be empty
. The reason is that theGitIgnoreManager
iterates over the segments of the path, which in one case is an empty string.Added a check for that and also added tests for this API. Apparently it wasn't tested yet.
I'm fixing a bug or typo
npm run add-contributor
and follow the prompts to add yourself to the README