Suggestion: `noAssignInExpressions` fixer is incorrect

Author: JP250552Created Jul 20, 2023Updated Jul 27, 2023

LabelsA-LinterL-JavaScript

Environment information

block

CLI:
  Version:                      12.1.3-nightly.f65b0d9
  Color support:                true

Platform:
  CPU Architecture:             aarch64
  OS:                           macos

Environment:
  ROME_LOG_DIR:                 unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v18.16.1"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "yarn/3.6.1"

Rome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    true
  VCS disabled:                 false

Workspace:
  Open Documents:               0

Discovering running Rome servers...

Incompatible Rome Server: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

ℹ Rage discovered this running server using an incompatible version of Rome.

Server:
  Version:                      12.1.3

What happened?

The fixer for noAssignInExpressions is transforming the statement to an equivalency check rather than the intended assignment.

Expected result

I'm not sure there should be a fixer on this rule without understanding the intent.

Code of Conduct

I agree to follow Rome's Code of Conduct

Source: rome/tools

View original on GitHub View discussion on GitHub