-
Notifications
You must be signed in to change notification settings - Fork 29.9k
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
Fixed mongodb typings implicit any error #26638
Fixed mongodb typings implicit any error #26638
Conversation
@vanwalj Thank you for submitting this PR! 🔔 @CaselIT @alanmarcell @kikar @bitjson @Dante-101 @mcortesi @EnricoPicci @AJCStriker @julien-c @daprahamian - please review this PR in the next few days. Be sure to explicitly select If no reviewer appears after a week, a DefinitelyTyped maintainer will review the PR instead. |
You are right, I didn’t saw that before. |
@vanwalj Unfortunately, this pull request currently has a merge conflict 😥. Please update your PR branch to be up-to-date with respect to master. Have a nice day! |
A definition owner has approved this PR ⭐️. A maintainer will merge this PR shortly. If it shouldn't be merged yet, please leave a comment saying so and we'll wait. Thank you for your contribution to DefinitelyTyped! |
Please fill in this template.
npm test
.)npm run lint package-name
(ortsc
if notslint.json
is present).I fixed a typing typo (I guess) where the argument name was missing and enabled the
noImplicitAny
option so it won't happen again !