jsx-eslint/eslint-plugin-react

Some cases should not be triggered **no-unused-state**

Open

#1,626 建立於 2017年12月25日

在 GitHub 查看
 (10 留言) (0 反應) (0 負責人)JavaScript (8,630 star) (2,797 fork)batch import
enhancementhelp wanted

描述

no-unused-state

state = {
  id: null,
  name: '',
  age: 0,
}

const {
  id,
  ...data
} = this.state;

console.log('data', data);

name and age should not be reported as error [eslint] Unused state field: 'departmentId' (react/no-unused-state).

貢獻者指南

技術棧
javascriptreact
領域
frontendtooling
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
ESLint plugin developmentAST traversalReact state patterns
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
45
研究方向
Examine the no unused state rule source code in lib/rules/no unused state.js. The false positive occurs when destructuring with rest operators (e.g., `const { id, ...data } = this.state`). The rule currently does not track that remaining properties are used via the rest variable. The fix should involve checking for assignments to rest elements or marking referenced rest variables as using all properties. Reviewing comments in issue #1626 for proposed solutions is recommended.