You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
React StrictMode should help with finding bugs in your React components. With
341
341
Reagent this unfortunately might not be helpful.
342
342
343
343
> Your components will re-render an extra time to find bugs caused by impure rendering.
344
344
> [Fixing bugs found by double rendering in development ](https://react.dev/reference/react/StrictMode#fixing-bugs-found-by-double-rendering-in-development)
345
345
346
+
[React v18, New Strict Mode Behaviors](https://react.dev/blog/2022/03/29/react-v18#new-strict-mode-behaviors)
347
+
346
348
In Reagent, triggering a side-effects from render functions has been somewhat
347
349
common use, though it is not recommended in React. The Reagent demo site timer-component
348
350
for example uses `js/setTimeout` directly in the render function to trigger
0 commit comments