synchronous rendering function #1912
-
|
we heavily use is there a hard blocker not to have a synchronous rendering function anymore? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
TL;DR yes, there is a hard blocker. The problem is that we are using React DOM under the hood, and it has the support for all sorts of things including handling thenables itself, so it is required for it to be async. The renderAsync has since been deprecated and will be dropped in the next major release (soon). This shouldn't have much impact because rendering is meant to be done at the moment of sending the email, and there is no way to send the email without async anyway. I wonder how your code base is structured to be a blocker here. |
Beta Was this translation helpful? Give feedback.
TL;DR yes, there is a hard blocker.
The problem is that we are using React DOM under the hood, and it has the support for all sorts of things including handling thenables itself, so it is required for it to be async. The renderAsync has since been deprecated and will be dropped in the next major release (soon).
This shouldn't have much impact because rendering is meant to be done at the moment of sending the email, and there is no way to send the email without async anyway. I wonder how your code base is structured to be a blocker here.