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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Breaking: Enable checkBooleanAssertions in no-negated-ok and no-ok-equality by default #193

Closed
wants to merge 1 commit into from

Conversation

platinumazure
Copy link
Owner

Fixes #190

@coveralls
Copy link

coveralls commented Jun 27, 2021

Coverage Status

Coverage remained the same at 100.0% when pulling 836c201 on check-boolean-assertions into 70f1f00 on master.

@bmish
Copy link
Collaborator

bmish commented Jun 28, 2021

Realistically, we could also just remove these options (so that boolean assertions are always included). There's not really any good reason for someone to ignore them (the option was only for backwards compatibility). But I'd be fine considering removal for the next major release v8).

@platinumazure
Copy link
Owner Author

@bmish You're right, I just wasn't thinking. I'm okay with removing the option altogether. I'll work on that this week sometime.

@bmish
Copy link
Collaborator

bmish commented Jul 13, 2021

This PR is replaced by #197

Copy link
Collaborator

@bmish bmish left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should close this PR in favor of #197.

@platinumazure platinumazure deleted the check-boolean-assertions branch January 3, 2023 05:42
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.

Enable checkBooleanAssertions options on no-negated-ok and no-ok-equality rules by default
3 participants