`Engine.render()` and `Engine.renderSync()` take generator as its first argument

When Page is a generator, Engine.render() and Engine.renderSync() take generator as its first argument, and returns generator which yields Data. I don’t feel this intuitive. They would better to take an iterated content and data as its argument, and returns string.

Also, Engine.render() can return generator, on the other hand, Engine.renderSync() cannot. I don’t think the typing here is correct.

[aiotter]

Anyway, now I know the current interface of Engine.render() and Engine.renderSync() is designed as intended. You can close the issue. Thanks for clarifying!

[aiotter]

I understand the reason why the returning type have to be unknown. Then what needed may be a fine document for creating Engine interface. I had to learn it by reading the standard plugins in this repository, and it seems I had much more to know about it.

As for my JSX engine, Nano JSX already uses Component#toString for rendering it, so I wasn’t able to override it for Lume. And you cannot export the result of function components, or even call them by yourself. Nano JSX require document variable in global scope to render them. This variable is defined by default in browsers as you know, and while rendering on deno, Nano JSX will define it inside Nano.renderSSR(). I don’t want to render the components twice while rendering layouts, but I have no idea better than that.