-
Notifications
You must be signed in to change notification settings - Fork 49
prefer-async-await
rule
#123
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
Comments
How would we want to detect that? See if there's a |
I was thinking checking whether there's a |
That could work well, only if we attempt to check the value of a variable if it's returned. This should be reported for instance test(t => {
var foo = fetch().then(data => {
t.is(data, 'foo');
});
return foo;
});
// or more realistically
test(t => {
var foo = fetch().then(fn);
var bar = foo.then(baz);
return bar;
}); I'm starting to use |
Oh man. That sucks. Backup though? 😜 |
I wish ^^' |
I don't usually push local work either, but I do have a close to real-time backup of my system using BackBlaze. It has saved me many times. |
Linux :( |
I see a lot of people doing:
When this would be much succinct:
Would be useful to have a rule to enforce using async/await.
The text was updated successfully, but these errors were encountered: