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
On the client, it's nice that development warnings are only triggered on the initial render. But, when rendering from the server with renderToString it's annoying to only have the warnings triggered the first render and then ignored on subsequent page loads.
What if render methods accepted an additional options argument?
Crazy ideas: This might be useful for other options too? Perhaps: appendToBody (auto-appends the second arg), or ignoreDOMCalls (automatically catches/ignores errors to for window and document APIs)?
The text was updated successfully, but these errors were encountered:
I'm going to close this out in favor of #4302, since that has been where most of the discussion has been taking place and I like the solution we arrived at in that thread.
On the client, it's nice that development warnings are only triggered on the initial render. But, when rendering from the server with
renderToString
it's annoying to only have the warnings triggered the first render and then ignored on subsequent page loads.What if render methods accepted an additional options argument?
Crazy ideas: This might be useful for other options too? Perhaps:
appendToBody
(auto-appends the second arg), orignoreDOMCalls
(automatically catches/ignores errors to forwindow
anddocument
APIs)?The text was updated successfully, but these errors were encountered: