om

Please ask the channel first, not @dnolen directly!
pedroteixeira 2017-05-24T01:43:24.894595Z

I was wondering if Om.Next would benefit from anything specific in the new React 16 (with fiber, etc)? Has any already tested the alpha?

anmonteiro 2017-05-24T01:49:22.941042Z

@pedroteixeira I tested an early version of Fiber and it works fine with Om Next

đź‘Ť 2
anmonteiro 2017-05-24T01:49:30.941953Z

there’s like 1 line of code that needs changing

anmonteiro 2017-05-24T01:50:27.949655Z

not sure we’ll benefit from anything apart from what every other person who’ll switch to it will also get

raspasov 2017-05-24T22:48:53.991456Z

@anmonteiro curious what’s that line? 🙂 (for the reason that I’m already using React 16 alpha via the React Native 0.44)

raspasov 2017-05-24T22:49:15.995802Z

I haven’t noticed anything weird, but curious in any case

raspasov 2017-05-24T22:52:28.033693Z

anmonteiro: got it, thanks! so basically just a change around the requires?

raspasov 2017-05-24T22:55:12.066211Z

don’t want to waste too much time, since there’s no problem atm 🙂 but I think the link goes to a diff with a bunch of small changes? https://github.com/omcljs/om/compare/master...anmonteiro:js-modules#diff-ee424e6559581b5b893371373a777e5eR188

anmonteiro 2017-05-24T22:55:48.073099Z

most don’t matter. the line I mean is changing goog.object/getValueByKeys to some->

raspasov 2017-05-24T22:56:04.076154Z

got it, thank you! 🙂