You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In reagent, we can just directly use react component by
[:> SomeComponent {} ...]
while sablono seems not support this.
Now I need to write wrapper functions which made the syntax not looked so concise compared with just using vector.
How about it?
The text was updated successfully, but these errors were encountered:
this has been asked a couple of times before. I'm not keen on extending the Sablono/Hiccup language with something like this at the moment, since it adds a lot more complexity. My main concern with something like this is server side rendering.
For now, I would suggest to wrap this in a function if you use this a lot.
Would be really nice to be able to refer to a React component class in place of a symbol. Something like [js/MyReactComponent {} ...], just as simple as [:div {} ...].
I didn't add this yet, because of server side rendering. How would that work? The only solution I had in mind so far is emitting a blank div or something like that.
Give it a try, but please keep the server side rendering in mind. Server side rendering is done via om.next at the moment, but since not much is happening with om.next I thought about borrowing that code and remove that dependency (which causes some problems already).
In
reagent
, we can just directly use react component bywhile sablono seems not support this.
Now I need to write wrapper functions which made the syntax not looked so concise compared with just using vector.
How about it?
The text was updated successfully, but these errors were encountered: