om

Please ask the channel first, not @dnolen directly!
Karol W贸jcik 2019-02-04T15:20:23.013800Z

What are your opinions about React.Fragment. It seems that it would be quite easy to add direct support for Fragment in om.dom using createElement function. It also seems that it will no be a breaking change :D

Karol W贸jcik 2019-02-04T15:20:33.014100Z

Is it worth adding?

wilkerlucio 2019-02-04T15:21:59.015100Z

@kwcharllie379 I guess the reason for om.next not having is just because nobody is sending new code for it, in Fulcro we did add on the primitives (since its not a DOM specific thing, works the same on RN), using it should be easy, you can take a look at the Fulcro impl: https://github.com/fulcrologic/fulcro/blob/8792813a1304f73a912e21a0945402055a8f9795/src/main/fulcro/client/primitives.cljc#L658

馃憤 1
2019-02-04T15:22:52.015500Z

I would definitely like to see it in om.next, it can be useful sometimes.

Karol W贸jcik 2019-02-04T15:26:38.016100Z

The question is whether the author is interested in that change.

Karol W贸jcik 2019-02-04T15:27:58.017500Z

Yes @wilkerlucio it seems quite easy to even add that function on one own. But I would rather have it in om.next

wilkerlucio 2019-02-04T15:33:32.018700Z

@kwcharllie379 AFAIK the author has no interest in maintaining it, in the past 2 years om.next only got updates from the author when some new cljs made it unusable because of some breaking change, other than that nothing had happened and I believe it will keep that way

Karol W贸jcik 2019-02-04T15:36:01.019900Z

I will try to create pr. We will see :D

馃憤 2