-
-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Object children are rendered as <undefined>
#245
Comments
Would you expect an error to be thrown instead or just skipping it? |
I don't really care as long as it matches what client side rendering does (which I think is skipping by default, or error if |
I think it would make most sense to always throw (because this is always user error), but I understand why that may not make sense as a default for |
My preference here is to silently ignore the object. We have throwing/warning in debug. |
Fragments are rendered as |
@pitust please file a new issue for that with details on how to reproduce it. Quickly checked on my end and rendering |
The text was updated successfully, but these errors were encountered: