Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add use-t-throws-async-well rule #278

Merged
merged 6 commits into from
Mar 8, 2020
Merged

Conversation

stroncium
Copy link
Contributor

@stroncium stroncium commented Sep 29, 2019

Fixes #274

Ensure that t.throwsAsync() and t.notThrowsAsync() aren't called without await(or some other action using returned promise).

馃


IssueHunt Summary

Referenced issues

This pull request has been submitted to:


IssueHunt has been backed by the following sponsors. Become a sponsor

docs/rules/use-t-throws-async-well.md Outdated Show resolved Hide resolved
docs/rules/use-t-throws-async-well.md Outdated Show resolved Hide resolved
@sindresorhus
Copy link
Member

sindresorhus commented Feb 19, 2020

Can you add an auto-fixer? It would just add await in front if it's missing, but only if the test implementation is an async function.

@stroncium
Copy link
Contributor Author

@sindresorhus done

@sindresorhus sindresorhus merged commit eea71c3 into avajs:master Mar 8, 2020
@sindresorhus
Copy link
Member

Looks good. IssueHunt is down, so remind me another day and I'll reward it.

@stroncium
Copy link
Contributor Author

@sindresorhus ping =D

@stroncium
Copy link
Contributor Author

@sindresorhus BTW, any info on how issuehunt is doing? Seems dying out to me.

@sindresorhus
Copy link
Member

@stroncium
Copy link
Contributor Author

stroncium commented Oct 7, 2020

Wait, I can access everything including issue pages.

What I meant is dying out as a project. It was the most promising one to put opensource on commercial rails.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

t.throwsAsync() and t.notThrowsAsync() should be awaited on
2 participants