Isomorphic rendering?

[DjebbZ]

Hello,

It's unclear from the Readme (and the Medium post). Does hicada supoort rendering the same component in both CLJ to a string and in CLJS ? We're using rum in a isomorphic setup and I'm interested to try out hicada.

[DjebbZ]

I've read briefly the code and I have my answers. To be able to use hicada in an isomorphic setup, I need to write my own html macro that emits the hiccup code as is in CLJ and does its job normally for CLJS. Which means my own macro should probably use something like macrovich to detect for which environment I want to compile the code.

[DjebbZ]

Or would you be interested into this feature for hicada itself ? (Sorry to reopen).

[rauhs]

Any non-breaking features are welcome :)

[DjebbZ]

Ok, I've been given more thought about the question. Currently one has to use rum or something like this to do the actual rendering to HTML on the JVM. I first thought that wasn't the case, in the sense that hicada was standalone.

You seem open to the feature, but there's no test coverage to know whether I break something if I try to implement it. What would be a good strategy?

[DjebbZ]

Rum happens to have a good strategy: it compares its own server side rendering with React.js itself on node and does isomorphic rendering to allow manual checking of the result in the browser. All with the same code.

Should hicada contains such a test suite? Something else?

[rauhs]

I don't think I'm interested in implementing (and maintaining) an HTML renderer. The rum one works great. I also think this is possible with the server-render? option, no?

[DjebbZ]

I understand. Indeed combining hicada and rum seems to work well enough. Feel free to close the issue (sending this message from my phone through email)

…

On Sat, Mar 2, 2019, 3:03 PM Andre R. ***@***.***> wrote: I don't think I'm interested in implementing (and maintaining) an HTML renderer. The rum one works great. I also think this is possible with the server-render? option, no? — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#9 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAEt3qNQQl8zJMRZrBC_Y5m2NPOOz7Fhks5vSoTKgaJpZM4azxN8> .

[niwinz]

I will close the issue but the server rendering will be considered probably in a near future.