'Pane' is defined but never used (@typescript-eslint/no-unused-vars)

'Text' is defined but never used (@typescript-eslint/no-unused-vars)

'Paragraph' is defined but never used (@typescript-eslint/no-unused-vars)

Error: Calling setState synchronously within an effect can trigger cascading renders

Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.

Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).

/home/runner/work/stuff/stuff/components/MailForm/DigestForm/Forms.tsx:64:13
  62 |         }
  63 |         if (hasInteractedName.current) {
> 64 |             setNameInvalid(name === '');
     |             ^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
  65 |         }
  66 |         if (hasInteractedDesc.current) {
  67 |             setDescInvalid(desc === ''); (react-hooks/set-state-in-effect)

Error: Calling setState synchronously within an effect can trigger cascading renders

Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.

Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).

/home/runner/work/stuff/stuff/components/MailForm/DigestForm/Forms.tsx:165:13
  163 |         }
  164 |         if (hasInteractedDesc.current) {
> 165 |             setDescInvalid(desc === '');
      |             ^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
  166 |         }
  167 |     }, [desc]);
  168 | (react-hooks/set-state-in-effect)

Error: Calling setState synchronously within an effect can trigger cascading renders

Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.

Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).

/home/runner/work/stuff/stuff/components/MailForm/DigestForm/Forms.tsx:249:13
  247 |         }
  248 |         if (hasInteractedName.current) {
> 249 |             setNameInvalid(name === '');
      |             ^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
  250 |         }
  251 |         if (hasInteractedDesc.current) {
  252 |             setDescInvalid(desc === ''); (react-hooks/set-state-in-effect)

Error: Calling setState synchronously within an effect can trigger cascading renders

Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.

Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).

/home/runner/work/stuff/stuff/components/PostPage.tsx:65:13
  63 |         const lastPage = data[data.length - 1];
  64 |         if (Array.isArray(lastPage) && lastPage.length === 0 && !finished) {
> 65 |             setFinished(true);
     |             ^^^^^^^^^^^ Avoid calling setState() directly within an effect
  66 |         }
  67 |     }, [data, finished]);
  68 | (react-hooks/set-state-in-effect)