-
Notifications
You must be signed in to change notification settings - Fork 230
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
bug: no-if doesn't work on nested ternary operators #557
Comments
For some reason I didn't seem to get a notification about this, but totally for the second one we should be erroring. For the function however, I think we shouldn't (which is the current behaviour if you use an
Thats taken from an active project of mine - while I do have that in a |
## [23.18.2](v23.18.1...v23.18.2) (2020-07-26) ### Bug Fixes * **no-if:** report conditionals in call expressions ([4cfcf08](4cfcf08)), closes [#557](#557)
🎉 This issue has been resolved in version 23.18.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
just discovered that if a ternary is nested inside a function call it will not be reported:
a couple examples of things that are not reporting:
The text was updated successfully, but these errors were encountered: