-
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 async doWhilst #8963
fixed async doWhilst #8963
Conversation
async/async.d.ts to authors (@borisyankov @Kern0 @Penryn). Could you review this PR? Checklist
|
Thanks for the contribution, but unfortunately this doesn't follow the API outlined at https://github.com/caolan/async#doWhilst 👎 |
Yes, but i think the API makes no sense at all, cause writing a test function without a parameter or a dataset which is testable is not really a test function ;-). |
You're welcome to open a ticket at caolan/async. Typescript definitions must exactly match a module's API regardless of your feelings for or against it. |
The API documentation is wrong and it's not about feelings. It's just working and correct. I already opened a ticket. |
Ok so looking at the changelog for this PR we had
Now replaced by
Looking at https://github.com/caolan/async/blob/master/lib/doWhilst.js#L29 I still don't think this is right. It seems @DominicBoettger you are right about that particular case (this is basically undocumented behavior). However, the existing repo isn't wrong (ie: no breaking changes), and these commits aren't right. Ideally, I still vote 👎, and welcome anyone else to weigh in! Perhaps a new PR should be opened to change |
Hello and thank you for your contribution! Due to an excessively long queue of pull requests that have become stale, we are "declaring bankruptcy" and closing all PRs opened before May 1, 2016. If you'd still like to merge this code in, please open a new PR that has been merged and rebased with the Going forward, we are committing to review or merge all PRs on a regular basis so this bankruptcy will not occur again. We apologize for the incovenience and hope you will continue to contribute to DefinitelyTyped in the future. Thanks |
No description provided.