[Suggestion]: Make useEffectEvent be usable by default in the challenges or add a new note for useRef's alternative
還沒有人認領這個 Issue。
- 主要語言
- JavaScript
- 星號
- 11.8k
- 分支
- 7.9k
- 平均合併
- 1 天 11 小時
- 30 天內合併 PR
- 11
描述
Summary
Make useEffectEvent be usable by default in Separating Events from Effects' challenges, or add a new note for useRef's alternative.
Page
https://react.dev/learn/separating-events-from-effects
Details
I attempted to solve the first challenge in Separating Events from Effects with useEffectEvent. First, following the previous example, I imported that function with this line:
import { experimental_useEffectEvent as useEffectEvent } from 'react';
Then, I used it with these lines:
const updateCount = useEffectEvent(() => {
setCount(c => c + increment);
});
However, this error was shown up:
Runtime Error
App.js: _react.experimental_useEffectEvent is not a function (8:37)
5 | const [count, setCount] = useState(0);
6 | const [increment, setIncrement] = useState(1);
7 |
> 8 | const updateCount = useEffectEvent(() => {
^
9 | setCount(c => c + increment);
10 | });
11 |
Therefore, by default, I can't use useEffectEvent for that exercise. I wrote "by default" because maybe it can be used by opening it in CodeSandbox. It looks like an extra effort for me, so I haven't tried it yet.
One of the solution I found for this challenge is using useRef. I think, the key for this challenge is how to avoid passing reactive elements to the Effect. Because useRef somehow can be treated as local variable which can be changed outside of render, and the interval itself is in-between render, I think it's safe to use. I need to make a Ref consistent with increment state. So, I modified each callback function of the increment buttons.
Here is my solution:
import { useState, useEffect, useRef } from 'react';
export default function Timer() {
const [count, setCount] = useState(0);
const [increment, setIncrement] = useState(1);
const incrementRef = useRef(1);
function decreaseIncrement() {
const prevIncrement = increment;
const newIncrement = prevIncrement - 1;
setIncrement(newIncrement);
incrementRef.current = newIncrement;
}
function increaseIncrement() {
const prevIncrement = increment;
const newIncrement = prevIncrement + 1;
setIncrement(newIncrement);
incrementRef.current = newIncrement;
}
useEffect(() => {
const id = setInterval(() => {
const localIncrement = incrementRef.current;
setCount(c => c + localIncrement);
}, 1000);
return () => {
clearInterval(id);
};
}, []);
return (
<>
<h1>
Counter: {count}
<button onClick={() => setCount(0)}>Reset</button>
</h1>
<hr />
<p>
Every second, increment by:
<button disabled={increment === 0} onClick={() => {
decreaseIncrement()
}}>–</button>
<b>{increment}</b>
<button onClick={() => {
increaseIncrement();
}}>+</button>
</p>
</>
);
}
It would be better if the useRef's alternative is included as a new note in Separating Events from Effects section.
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
從 Separating Events from Effects 頁面開始,使用文件中說明的 useEffectEvent import 重現第一個 challenge。判斷 challenge 環境是否應支援該 API,或頁面是否應說明 useRef 替代方案;當選定的方法已在 challenge 及其相關指引中可用或獲得清楚說明時,即表示完成。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- javascript, react
- 領域
- documentation
- Issue 類型
- 文件
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 停滯
- 描述清晰度
- 基本清楚
- 新手友好度
- 38/100