We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently instantly resolves. I think this should be a case we throw an error in.
The text was updated successfully, but these errors were encountered:
I agree, a limit of 0 or less would certainly be a programmer error.
It's weird that we have a test for the old behavior. I'm not sure how limit 0 would be useful to anyone.
Sorry, something went wrong.
Definitely throw an error.
Please also throw on undefined. That would have made finding my async.eachLimit(list, config.propWithType, fn) bug way easier.
async.eachLimit(list, config.propWithType, fn)
No branches or pull requests
Currently instantly resolves. I think this should be a case we throw an error in.
The text was updated successfully, but these errors were encountered: