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
When using useDirective in react with a directive that runs server-side and adds some attributes, the generated markup on the server does not match the generated markup on the client (as seen by react).
As part of #698, to avoid the hydration warning raised by react, I had initially added suppressHydrationWarning in useDirective. @quentinderoubaixsuggested to remove it and I followed his suggestion, but now we have warnings in development mode when using AgnosUI components with SSR.
Should we solve this by simply adding back suppressHydrationWarning or should we find a better solution?
The text was updated successfully, but these errors were encountered:
When using
useDirective
in react with a directive that runs server-side and adds some attributes, the generated markup on the server does not match the generated markup on the client (as seen by react).As part of #698, to avoid the hydration warning raised by react, I had initially added
suppressHydrationWarning
inuseDirective
.@quentinderoubaix suggested to remove it and I followed his suggestion, but now we have warnings in development mode when using AgnosUI components with SSR.
Should we solve this by simply adding back
suppressHydrationWarning
or should we find a better solution?The text was updated successfully, but these errors were encountered: