Skip to content

fix: no-unused-vars include caught errors pattern in report message#18609

Merged
snitin315 merged 2 commits intoeslint:mainfrom
kirkwaiblinger:caught-errors-for-written-but-not-read
Jun 21, 2024
Merged

fix: no-unused-vars include caught errors pattern in report message#18609
snitin315 merged 2 commits intoeslint:mainfrom
kirkwaiblinger:caught-errors-for-written-but-not-read

Conversation

@kirkwaiblinger
Copy link
Copy Markdown
Contributor

Prerequisites checklist

What is the purpose of this pull request? (put an "X" next to an item)

[ ] Documentation update
[x] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:

fix #18607

What changes did you make? (Give an overview)

Extracted report description inference to a common helper to reduce errors.

Depends on/blocked by #18608

Is there anything you'd like reviewers to focus on?

@kirkwaiblinger kirkwaiblinger requested a review from a team as a code owner June 19, 2024 23:09
@eslint-github-bot eslint-github-bot Bot added the bug ESLint is working incorrectly label Jun 19, 2024
@github-actions github-actions Bot added the rule Relates to ESLint's core rules label Jun 19, 2024
@netlify
Copy link
Copy Markdown

netlify Bot commented Jun 19, 2024

Deploy Preview for docs-eslint canceled.

Name Link
🔨 Latest commit e514097
🔍 Latest deploy log https://app.netlify.com/sites/docs-eslint/deploys/667441ebe9b3650008ba484c

@kirkwaiblinger kirkwaiblinger force-pushed the caught-errors-for-written-but-not-read branch from 17eefe0 to cd59b01 Compare June 19, 2024 23:28
@mdjermanovic
Copy link
Copy Markdown
Member

#18608 has been merged now, but it caused merge conflicts here.

@mdjermanovic mdjermanovic added accepted There is consensus among the team that this change meets the criteria for inclusion contributor pool labels Jun 20, 2024
@kirkwaiblinger kirkwaiblinger force-pushed the caught-errors-for-written-but-not-read branch from cd59b01 to d23dc2e Compare June 20, 2024 14:16
@kirkwaiblinger
Copy link
Copy Markdown
Contributor Author

@mdjermanovic updated 👍

Copy link
Copy Markdown
Member

@mdjermanovic mdjermanovic left a comment

Choose a reason for hiding this comment

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

LGTM, thanks! Leaving open for one day in case anyone else would like to take a look.

@mdjermanovic mdjermanovic changed the title fix: [no-unused-vars] Include caught errors pattern in report message fix: no-unused-vars include caught errors pattern in report message Jun 20, 2024
@snitin315 snitin315 merged commit 21d3766 into eslint:main Jun 21, 2024
@kirkwaiblinger kirkwaiblinger deleted the caught-errors-for-written-but-not-read branch June 21, 2024 13:35
@eslint-github-bot eslint-github-bot Bot locked and limited conversation to collaborators Dec 19, 2024
@eslint-github-bot eslint-github-bot Bot added the archived due to age This issue has been archived; please open a new issue for any further discussion label Dec 19, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

accepted There is consensus among the team that this change meets the criteria for inclusion archived due to age This issue has been archived; please open a new issue for any further discussion bug ESLint is working incorrectly contributor pool rule Relates to ESLint's core rules

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

Bug: [no-unused-vars] Error message doesn't inform about caught errors pattern when caught error is reassigned but not used

3 participants