-
Notifications
You must be signed in to change notification settings - Fork 38
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
Clean up threw
assertions
#81
Comments
I looked into this, and it's probably easier to manually change stuff like try
foo();
assert.okay(foo.threw, 'error message') to try
foo();
assert.fail('error message') |
Do you have a list of places where this appears in code? Is this something we can lint for? |
Yes, we could lint for this. It could be added to #79, or be a new issue. |
Let's do a new issue for the linting rule. I'll tackle updating those instances. |
Let's set this aside for now. This is basically discussing a new rule (prefer |
We still have
assert.okay(foo.threw, 'error message')
-style assertions. These should probably be converted toassert.fail('error message';)
, or the original CoffeeScript should be altered to not use this pattern.The text was updated successfully, but these errors were encountered: