Skip to content

feat(eslint-plugin): [strict-boolean-expressions] check array predicate functions' return statements #10106

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

Conversation

ronami
Copy link
Member

@ronami ronami commented Oct 5, 2024

PR Checklist

Overview

This PR addresses #8016 and updates strict-boolean-expressions to check for array predicate return statements.

Two things to note:

Doesn't handle implicit returns

I didn't handle implicit return types from array predicates since I'm not sure if the rule should cover this:

[1, null].filter(x => {
  if (x) {
    return true;
  }

  // implicitly returns `undefined`
});

Please let me know if you think it should.

Somewhat of a breaking change

This is a breaking change, though the issue itself isn't marked as one, and according to the docs:

A change to the plugins shall not be considered breaking if it:

  • Adds additional checks to an existing rule that causes new reports in a small-to-medium set of cases in an average codebase.

Alternatively, I can put this behind a flag, which can be removed in a later version.

@typescript-eslint
Copy link
Contributor

Thanks for the PR, @ronami!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!


🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint.

Copy link

netlify bot commented Oct 5, 2024

Deploy Preview for typescript-eslint ready!

Name Link
🔨 Latest commit f17a05c
🔍 Latest deploy log https://app.netlify.com/sites/typescript-eslint/deploys/676d2a75a34d9400096b00f1
😎 Deploy Preview https://deploy-preview-10106--typescript-eslint.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 98 (🟢 up 25 from production)
Accessibility: 100 (no change from production)
Best Practices: 92 (no change from production)
SEO: 98 (no change from production)
PWA: 80 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

nx-cloud bot commented Oct 5, 2024

View your CI Pipeline Execution ↗ for commit f17a05c.

Command Status Duration Result
nx test eslint-plugin --coverage=false ✅ Succeeded 7m 13s View ↗
nx test eslint-plugin ✅ Succeeded 6m 1s View ↗
nx test visitor-keys --coverage=false ✅ Succeeded <1s View ↗
nx test utils --coverage=false ✅ Succeeded <1s View ↗
nx test typescript-eslint --coverage=false ✅ Succeeded 8s View ↗
nx test type-utils --coverage=false ✅ Succeeded <1s View ↗
nx run types:build ✅ Succeeded <1s View ↗
nx run-many --target=build --exclude website --... ✅ Succeeded 31s View ↗
Additional runs (24) ✅ Succeeded ... View ↗

☁️ Nx Cloud last updated this comment at 2024-12-26 10:20:31 UTC

@ronami ronami changed the title Strict boolean expressions predicates feat(eslint-plugin): [strict-boolean-expressions] Check array predicate return statements Oct 5, 2024
@ronami ronami changed the title feat(eslint-plugin): [strict-boolean-expressions] Check array predicate return statements feat(eslint-plugin): [strict-boolean-expressions] Check array predicate functions' return statements Oct 5, 2024
@ronami ronami changed the title feat(eslint-plugin): [strict-boolean-expressions] Check array predicate functions' return statements feat(eslint-plugin): [strict-boolean-expressions] check array predicate functions' return statements Oct 5, 2024
Copy link

codecov bot commented Oct 5, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.86%. Comparing base (5a39e0c) to head (f17a05c).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #10106      +/-   ##
==========================================
+ Coverage   86.84%   86.86%   +0.02%     
==========================================
  Files         445      445              
  Lines       15427    15455      +28     
  Branches     4497     4507      +10     
==========================================
+ Hits        13397    13425      +28     
  Misses       1675     1675              
  Partials      355      355              
Flag Coverage Δ
unittest 86.86% <100.00%> (+0.02%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
...int-plugin/src/rules/strict-boolean-expressions.ts 100.00% <100.00%> (ø)

@ronami ronami marked this pull request as ready for review October 5, 2024 06:54
Copy link
Member

@JoshuaKGoldberg JoshuaKGoldberg left a comment

Choose a reason for hiding this comment

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

Nice! One discussion on implicit undefined return, and some requests around testing. Direction seems great to me! 🚀

Comment on lines 168 to 171
x.filter(t => {
return t ? 1 : 0;
});
x.filter(t => !t);
Copy link
Member

Choose a reason for hiding this comment

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

[Testing] We generally try to stick to one thing under test for each test case. For this one, it looks like two things are being tested:

  • That the allowNullableBoolean option still works...
  • ...and that general logic holds true for all three variations of something passed to .filter

I don't think the latter is necessary. We can trim the tests down a bit:

Suggested change
x.filter(t => {
return t ? 1 : 0;
});
x.filter(t => !t);

Here and the other ones with several variations of the same, such as allowNullableString: true.

@JoshuaKGoldberg JoshuaKGoldberg added the awaiting response Issues waiting for a reply from the OP or another party label Oct 10, 2024
@ronami
Copy link
Member Author

ronami commented Dec 17, 2024

btw - sorry for taking so long to get around to a review on this!

No problem, I appreciate your assistance with the PR, it's been very helpful 👍

Copy link
Member

@kirkwaiblinger kirkwaiblinger left a comment

Choose a reason for hiding this comment

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

home stretch!

Copy link
Member

@kirkwaiblinger kirkwaiblinger left a comment

Choose a reason for hiding this comment

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

I think we're there! Great work on this! I'm excited to get to use this feature ❤️

@kirkwaiblinger kirkwaiblinger added the 1 approval >=1 team member has approved this PR; we're now leaving it open for more reviews before we merge label Dec 26, 2024
@kirkwaiblinger kirkwaiblinger requested review from JoshuaKGoldberg and removed request for JoshuaKGoldberg December 26, 2024 10:23
@github-actions github-actions bot removed the 1 approval >=1 team member has approved this PR; we're now leaving it open for more reviews before we merge label Dec 26, 2024
@kirkwaiblinger kirkwaiblinger added the 1 approval >=1 team member has approved this PR; we're now leaving it open for more reviews before we merge label Dec 26, 2024
Copy link
Member

@JoshuaKGoldberg JoshuaKGoldberg left a comment

Choose a reason for hiding this comment

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

So thorough, love it! 🚀

@JoshuaKGoldberg JoshuaKGoldberg merged commit 07d0e0d into typescript-eslint:main Dec 26, 2024
68 checks passed
@ronami ronami deleted the strict-boolean-expressions-predicates branch December 26, 2024 23:09
renovate bot added a commit to mmkal/eslint-plugin-mmkal that referenced this pull request Dec 30, 2024
##### [v8.19.0](https://github.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#8190-2024-12-30)

##### 🚀 Features

-   **eslint-plugin:** \[strict-boolean-expressions] check array predicate functions' return statements ([#10106](typescript-eslint/typescript-eslint#10106))

##### 🩹 Fixes

-   **eslint-plugin:** \[member-ordering] ignore method overloading ([#10536](typescript-eslint/typescript-eslint#10536))
-   **eslint-plugin:** \[consistent-indexed-object-style] don't report on indirect circular references ([#10537](typescript-eslint/typescript-eslint#10537))
-   **eslint-plugin:** \[array-type] autofix with conditional types needs parentheses ([#10522](typescript-eslint/typescript-eslint#10522))
-   **eslint-plugin:** add getConstraintInfo to handle generic constraints better ([#10496](typescript-eslint/typescript-eslint#10496))

##### ❤️ Thank You

-   Karl Werner
-   Kirk Waiblinger [@kirkwaiblinger](https://github.com/kirkwaiblinger)
-   Ronen Amiel
-   YeonJuan [@yeonjuan](https://github.com/yeonjuan)

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.
renovate bot added a commit to andrei-picus-tink/auto-renovate that referenced this pull request Dec 31, 2024
| datasource | package                          | from   | to     |
| ---------- | -------------------------------- | ------ | ------ |
| npm        | @typescript-eslint/eslint-plugin | 8.18.2 | 8.19.0 |
| npm        | @typescript-eslint/parser        | 8.18.2 | 8.19.0 |


## [v8.19.0](https://github.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#8190-2024-12-30)

##### 🚀 Features

-   **eslint-plugin:** \[strict-boolean-expressions] check array predicate functions' return statements ([#10106](typescript-eslint/typescript-eslint#10106))

##### 🩹 Fixes

-   **eslint-plugin:** \[member-ordering] ignore method overloading ([#10536](typescript-eslint/typescript-eslint#10536))
-   **eslint-plugin:** \[consistent-indexed-object-style] don't report on indirect circular references ([#10537](typescript-eslint/typescript-eslint#10537))
-   **eslint-plugin:** \[array-type] autofix with conditional types needs parentheses ([#10522](typescript-eslint/typescript-eslint#10522))
-   **eslint-plugin:** add getConstraintInfo to handle generic constraints better ([#10496](typescript-eslint/typescript-eslint#10496))

##### ❤️ Thank You

-   Karl Werner
-   Kirk Waiblinger [@kirkwaiblinger](https://github.com/kirkwaiblinger)
-   Ronen Amiel
-   YeonJuan [@yeonjuan](https://github.com/yeonjuan)

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 3, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
1 approval >=1 team member has approved this PR; we're now leaving it open for more reviews before we merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Enhancement: [strict-boolean-expressions] Check array filter/find predicate functions as boolean locations.
3 participants