Thanks to visit codestin.com
Credit goes to github.com

Skip to content

fix(eslint-plugin): [no-unnecessary-condition] improve error message for literal comparisons #10194

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

Merged

Conversation

kirkwaiblinger
Copy link
Member

PR Checklist

Overview

In addition to changing the wording, I've also had the error message compute whether the condition is actually true or false.

@typescript-eslint
Copy link
Contributor

Thanks for the PR, @kirkwaiblinger!

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 22, 2024

Deploy Preview for typescript-eslint ready!

Name Link
🔨 Latest commit eb9ad53
🔍 Latest deploy log https://app.netlify.com/sites/typescript-eslint/deploys/6728f70774cffd00088aaedc
😎 Deploy Preview https://deploy-preview-10194--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: 99 (no change 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 22, 2024

☁️ Nx Cloud Report

CI is running/has finished running commands for commit eb9ad53. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution


✅ Successfully ran 2 targets

Sent with 💌 from NxCloud.

@kirkwaiblinger kirkwaiblinger force-pushed the nuc-literal-comparisons branch 2 times, most recently from 5a3d55b to e28ee68 Compare October 22, 2024 06:24
@kirkwaiblinger kirkwaiblinger force-pushed the nuc-literal-comparisons branch from e28ee68 to c7adb29 Compare October 22, 2024 06:28
Copy link

codecov bot commented Oct 22, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.52%. Comparing base (f83a591) to head (eb9ad53).
Report is 5 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #10194      +/-   ##
==========================================
+ Coverage   86.51%   86.52%   +0.01%     
==========================================
  Files         430      430              
  Lines       15124    15144      +20     
  Branches     4399     4404       +5     
==========================================
+ Hits        13084    13104      +20     
  Misses       1683     1683              
  Partials      357      357              
Flag Coverage Δ
unittest 86.52% <100.00%> (+0.01%) ⬆️

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

Files with missing lines Coverage Δ
...slint-plugin/src/rules/no-unnecessary-condition.ts 99.20% <100.00%> (+0.06%) ⬆️

@kirkwaiblinger kirkwaiblinger marked this pull request as ready for review October 22, 2024 15:26
tsutils.isBooleanLiteralType(type) ||
type.flags === ts.TypeFlags.Undefined ||
type.flags === ts.TypeFlags.Null ||
type.flags === ts.TypeFlags.Void ||
Copy link
Member Author

@kirkwaiblinger kirkwaiblinger Oct 22, 2024

Choose a reason for hiding this comment

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

Note that I intentionally omitted the void check.

  1. It is not tested for
  2. We've gone towards thinking of void as unknown in terms of its possible values, rather than undefined only. And if it doesn't have a specific, knowable value such that we can precompute the condition... then it's an indication that we can't in good faith tell the user the condition is unnecessary due to both sides of the condition being known literal values.
  3. Also I think TS bans most relevant usages of it anyways

@kirkwaiblinger
Copy link
Member Author

Note to self: align impl with changes in #10205

line,
messageId,
});

Copy link
Member

Choose a reason for hiding this comment

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

[Praise] Nice cleanup 😄

JoshuaKGoldberg
JoshuaKGoldberg previously approved these changes Nov 4, 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.

The word 'Stellar' above a black sky, with a light effect tracing the 'S'

@JoshuaKGoldberg
Copy link
Member

Note to self: align impl with changes in #10205

@kirkwaiblinger is there anything you still want to do here? I think it's ready for merge if not.

@JoshuaKGoldberg JoshuaKGoldberg added the 1 approval >=1 team member has approved this PR; we're now leaving it open for more reviews before we merge label Nov 4, 2024
@kirkwaiblinger
Copy link
Member Author

kirkwaiblinger commented Nov 4, 2024

@kirkwaiblinger is there anything you still want to do here? I think it's ready for merge if not.

yeah, there's a bit of duplicated code, lemme just merge from main and clean that up 👍

@JoshuaKGoldberg JoshuaKGoldberg added awaiting response Issues waiting for a reply from the OP or another party and removed 1 approval >=1 team member has approved this PR; we're now leaving it open for more reviews before we merge labels Nov 4, 2024
@kirkwaiblinger kirkwaiblinger removed the awaiting response Issues waiting for a reply from the OP or another party label Nov 4, 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.

👍

@JoshuaKGoldberg JoshuaKGoldberg merged commit 22f7f25 into typescript-eslint:main Nov 4, 2024
67 of 69 checks passed
@kirkwaiblinger kirkwaiblinger deleted the nuc-literal-comparisons branch November 4, 2024 22:33
renovate bot added a commit to mmkal/eslint-plugin-mmkal that referenced this pull request Nov 11, 2024
##### [v8.14.0](https://github.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#8140-2024-11-11)

##### 🚀 Features

-   **eslint-plugin:** \[await-thenable] report unnecessary `await using` statements ([#10209](typescript-eslint/typescript-eslint#10209))
-   **eslint-plugin:** \[no-confusing-void-expression] add an option to ignore void<->void ([#10067](typescript-eslint/typescript-eslint#10067))

##### 🩹 Fixes

-   **scope-manager:** fix asserted increments not being marked as write references ([#10271](typescript-eslint/typescript-eslint#10271))
-   **eslint-plugin:** \[no-misused-promises] improve report loc for methods ([#10216](typescript-eslint/typescript-eslint#10216))
-   **eslint-plugin:** \[no-unnecessary-condition] improve error message for literal comparisons ([#10194](typescript-eslint/typescript-eslint#10194))

##### ❤️  Thank You

-   Gyumong [@gyumong](https://github.com/Gyumong)
-   Jan Ochwat [@janek515](https://github.com/janek515)
-   Kirk Waiblinger [@kirkwaiblinger](https://github.com/kirkwaiblinger)
-   Ronen Amiel

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 Nov 12, 2024
| datasource | package                          | from   | to     |
| ---------- | -------------------------------- | ------ | ------ |
| npm        | @typescript-eslint/eslint-plugin | 8.13.0 | 8.14.0 |
| npm        | @typescript-eslint/parser        | 8.13.0 | 8.14.0 |


## [v8.14.0](https://github.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#8140-2024-11-11)

##### 🚀 Features

-   **eslint-plugin:** \[await-thenable] report unnecessary `await using` statements ([#10209](typescript-eslint/typescript-eslint#10209))
-   **eslint-plugin:** \[no-confusing-void-expression] add an option to ignore void<->void ([#10067](typescript-eslint/typescript-eslint#10067))

##### 🩹 Fixes

-   **scope-manager:** fix asserted increments not being marked as write references ([#10271](typescript-eslint/typescript-eslint#10271))
-   **eslint-plugin:** \[no-misused-promises] improve report loc for methods ([#10216](typescript-eslint/typescript-eslint#10216))
-   **eslint-plugin:** \[no-unnecessary-condition] improve error message for literal comparisons ([#10194](typescript-eslint/typescript-eslint#10194))

##### ❤️  Thank You

-   Gyumong [@gyumong](https://github.com/Gyumong)
-   Jan Ochwat [@janek515](https://github.com/janek515)
-   Kirk Waiblinger [@kirkwaiblinger](https://github.com/kirkwaiblinger)
-   Ronen Amiel

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 Nov 12, 2024
| datasource | package                          | from   | to     |
| ---------- | -------------------------------- | ------ | ------ |
| npm        | @typescript-eslint/eslint-plugin | 8.13.0 | 8.14.0 |
| npm        | @typescript-eslint/parser        | 8.13.0 | 8.14.0 |


## [v8.14.0](https://github.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#8140-2024-11-11)

##### 🚀 Features

-   **eslint-plugin:** \[await-thenable] report unnecessary `await using` statements ([#10209](typescript-eslint/typescript-eslint#10209))
-   **eslint-plugin:** \[no-confusing-void-expression] add an option to ignore void<->void ([#10067](typescript-eslint/typescript-eslint#10067))

##### 🩹 Fixes

-   **scope-manager:** fix asserted increments not being marked as write references ([#10271](typescript-eslint/typescript-eslint#10271))
-   **eslint-plugin:** \[no-misused-promises] improve report loc for methods ([#10216](typescript-eslint/typescript-eslint#10216))
-   **eslint-plugin:** \[no-unnecessary-condition] improve error message for literal comparisons ([#10194](typescript-eslint/typescript-eslint#10194))

##### ❤️  Thank You

-   Gyumong [@gyumong](https://github.com/Gyumong)
-   Jan Ochwat [@janek515](https://github.com/janek515)
-   Kirk Waiblinger [@kirkwaiblinger](https://github.com/kirkwaiblinger)
-   Ronen Amiel

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 Nov 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bug: [no-unnecessary-condition] Confusing message when comparing a variable to all possible values
2 participants