render_jsx() Function

[Archmonger]

Current Situation

In order to render JSX, currently custom components are needed.

Proposed Actions

Create an idom.jsx.render function that can output JSX to VDOM.

See python-react for design inspiration.

Implementation Details

The interface would look something like this...

@idom.component
def my_component():
    return idom.jsx.render("/path/to/component.jsx", {"foo":"bar"})

@idom.component
def my_second_component():
    # Also, we should try to make it play nicely with standard IDOM templating
    return h1(
        "Hello World",
         idom.jsx.render("/path/to/component.jsx",
         {"foo":"bar"},
         ),    
    )

[Archmonger]

This would be an amazingly useful developer utility that would effectively make custom components obsolete.
But as of right now is not a MVP feature. So I think this should get developed during v1 -> v2

[Archmonger]

@rmorshea Also I'm realizing the awkwardness of the GitHub projects titles.

It's hard to tell if 1.x Release means that all of those features are required to reach V1, or if those tasks will be developed while in V1.

Maybe rename sections to v0 to v1.0 Milestone, v1.0 to v2.0 Milestone, and v2.0 to v3.0 Milestone

[rmorshea]

I think this can probably be wrapped up in the #578 issue. Ultimately there may be different ways of doing server-side rendering in IDOM, but at least to start, we'll probably want to just pick one to start.

[Archmonger]

JSX rendering can be done in multiple ways, and can possibly be server side render or client side.

I'm thinking of this specific ticket as a "custom components 2.0"

[rmorshea]

The custom components interface is a bit more general than this. It doesn't make assumptions about how the components are implemented - it might be React, but it doesn't have to be. Thus, a feature like this would probably be implemented as a custom component that reaches out to a react render server endpoint.