Change from `null` to `undefined` introduces issues with `<value> !== undefined`

未關閉
#673 2 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
48/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
冷清
技術堆疊
react, typescript
領域
frontend

研究方向

Start with the TextField.tsx line linked in the issue, then follow the investigation in the linked comment and check Modal, Popover, Grid, and GridSpan, especially generateResponsiveCustomProperties. Review how each prop handles null and undefined, and decide whether defaulted props support null or need documentation. Done means resolving the listed checks and documenting the behavior decision.

由索引模型根據 Issue 內容生成。

描述

bug

This is caused by https://github.com/react-ui-org/react-ui/issues/662


As result of mentioned change, TextField is incorrectly setting hasRootSmallInput class when inputSize is set to null. This is happening on following line: https://github.com/react-ui-org/react-ui/blob/71b2fe1cd5719128ebdf3d17b90f4b441ebe199d/src/components/TextField/TextField.tsx#L38

Problem is that if inputSize is set to null:

const hasSmallInput = (inputSize !== undefined) && (inputSize <= SMALL_INPUT_SIZE);

Then hasSmallInput is true because of inputSize <= SMALL_INPUT_SIZE => true. Why? Because null <= 10 ...

We need to investigate this and examine all occurrences of !== undefined and !== null as well. This is why I always recommend using != null to cover both cases.

Scope

Investigated in https://github.com/react-ui-org/react-ui/issues/673#issuecomment-5998585636.

  • Use != null in TextField, Modal and Popover (caused by #662)
  • Use prop == null in generateResponsiveCustomProperties (Grid, GridSpan)
  • Decide whether null is supported for props with defaults (Popover placement, tag, …), or document that only undefined means "not set"
主要語言
TypeScript
星號
23
分支
10
平均合併
5 天 12 小時
30 天內合併 PR
9

環境準備

在 Codespaces 中開啟

在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 沒有貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

react-ui-org/react-ui 的其他 Issue

查看 react-ui-org/react-ui 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。