Thoughts on extending the API

Hi again!

Consider a scenario where inside of getComponent, we’d like to return a React component rendered with either with renderReact or renderReactStatic, depending on the context (eg legacy reasons).

My initial thought is that we could do something funky like define NameOfComponent and NameOfComponentStatic and pass such args though the component name.

What would be even better though is to be able to define custom args; something like

{
  "NameOfComponent": {
    "name": "NameOfComponent",
    "args": {
       "renderType": "static",
    },
    "data": {
      "theseAreProps": true,
      "someOtherProps": ["one", "two", "three"]
    },
  }
}

and args gets passed alongside name to getComponent.

Does this seem reasonable? Thanks!

[goatslacker]

Yes this sort of logic is best served by a hypernova-client like hypernova-react.

A hypernova client is just a function so you can do and return whatever you’d like.

[goatslacker]

I still need a way to pass the ‘isStatic’ flag (amongst other server only args) through to Hypernova from the clientlib 😃

I see, so your other server is the one that holds the knowledge on whether you want to render something static or non-static. If thats’ the case you can pass that sort of information down with the initial payload:

{
  renderStyle: 'static',
  componentProps: serializableProps,
}