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

feat(linter): implement eslint/no-multi-assign #8158

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

AnsonH
Copy link
Contributor

@AnsonH AnsonH commented Dec 28, 2024

Implements eslint/no-multi-assign rule.

Copy link

graphite-app bot commented Dec 28, 2024

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • 0-merge - adds this PR to the back of the merge queue
  • hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

@github-actions github-actions bot added A-linter Area - Linter C-enhancement Category - New feature or request labels Dec 28, 2024
Copy link

codspeed-hq bot commented Dec 28, 2024

CodSpeed Performance Report

Merging #8158 will not alter performance

Comparing AnsonH:feat/linter/no-multi-assign (2fe2bb2) with main (37c9959)

Summary

✅ 29 untouched benchmarks

Comment on lines +5 to +9
⚠ eslint(no-multi-assign): Do not use chained assignment
╭─[no_multi_assign.tsx:1:9]
1 │ var a = b = c;
· ─────
╰────
Copy link
Contributor

Choose a reason for hiding this comment

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

can we add a help describing either why this is bad or how to fix?

Consider moving this into two separate assignments... or something similar

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-linter Area - Linter C-enhancement Category - New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants