[feat] no-set-state-directly-in-use-effect

[SukkaW]

Describe the problem

Common bad practice:

const Comp = () => {
  const [data, setData] = useState();
  useEffect(() => {
    setData();
  }, []);
}

Describe the solution you'd like

Create a rule no-set-state-directly-in-use-effect to prevent set state directly in the top useEffect callback scope:

Invalid

const Comp = () => {
  const [data, setData] = useState();
  useEffect(() => {
    setData();
  }, []);
}

Valid

const Comp = () => {
  const [data, setData] = useState();
  useEffect(() => {
   fetch().then(() => setData());
  }, []);
}

const Comp = () => {
  const [data, setData] = useState();
  useEffect(() => {
   (async () => { setData() })();
  }, []);
}

const Comp = () => {
  const [data, setData] = useState();
  useEffect(() => {
   const onLoad = () => {
     setData();
   };
  }, []);
}

Alternatives considered

No response

Additional context

No response