Object children are rendered as <undefined>

[lucacasonato]

import render from "https://esm.sh/[email protected][email protected]";
import { h } from "https://esm.sh/[email protected]";
console.log(render(h("div", null, { hello: "world" })));

$ deno run test.ts
<div><undefined></undefined></div>

[JoviDeCroock]

Would you expect an error to be thrown instead or just skipping it?

[lucacasonato]

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 preact/debug is loaded).

[lucacasonato]

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 preact due to possible size implications.

[developit]

My preference here is to silently ignore the object. We have throwing/warning in debug.

[pitust]

Fragments are rendered as <undefined>stuff inside the fragment</undefined>, which is undesirable as well.

[marvinhagemeister]

@pitust please file a new issue for that with details on how to reproduce it. Quickly checked on my end and rendering Fragments works as expected.