appsmithorg/appsmith

(JS-0458) Definitions for unused states detected

Open

#7,943 opened on 2021年9月29日

GitHub で見る
 (20 comments) (0 reactions) (1 assignee)TypeScript (39,454 stars) (4,508 forks)batch import
Good First IssueLow effortTask

説明

Description

You should avoid defining states that are not being used because unused states might affect while refactoring the codebase and introduces unnecessary operations by ReactJS. It is recommended to plan the behavior and operation of the component.

Occurrences

There are 9 occurrences of this issue in the repository.

See all occurrences on DeepSource → deepsource.io/gh/appsmithorg/appsmith/issue/JS-0458/occurrences/

コントリビューターガイド

技術スタック
typescriptreact
領域
frontend
Issue 種別
refactor
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
2
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-3 hours
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
active
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Basic React knowledgeUnderstanding of component stateFamiliarity with code editing
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
70
調査方針
Review the 9 occurrences listed in the DeepSource link (deepsource.io/gh/appsmithorg/appsmith/issue/JS 0458/occurrences/). Each occurrence points to a file and line number where an unused state definition is detected. For each case, verify that the state variable is indeed not used anywhere in the component or its children. If unused, remove the state definition and any associated setter calls. Ensure that the component still functions correctly by checking for any indirect usage. The repository is TypeScript based React, so look for useState calls in function components. The issue has an assignee, so coordinate if necessary.
(JS-0458) Definitions for unused states detected · appsmithorg/appsmith#7943 | Good First Issue