Fork me on GitHub
#om
<
2017-02-11
>
therabidbanana00:02:26

After some bisecting - yeah, it was definitely the switch from alpha46 to alpha47 that changed this behavior in our app. Not sure if that's just because it's exposing a bug in our app (we had some other weird things the transition to 47 exposed with queries not composing up to the root in some cases, maybe this is like that)

therabidbanana00:02:19

Okay - it was because of ^:once - don't know how that never bit us before! Thanks for pointing me in the right direction @adambros. When I tried to fix it earlier with that I think I screwed up how I added it in the macro. (changed to ~(with-meta name {:once true}) instead of ^:once ~name)

adambros00:02:14

yeah i’ve run into that, really annoying

sineer07:02:00

Is it possible to somehow "extend" an om component? Like using polymorphism to inherit some BaseComponent that was defined using defui ?

levitanong20:02:05

hi all, in om.next, is there a way to force a re-render of a component, bypassing the render queue? I ask because when using om.next with react-native, controlled TextInputs end up stuttering. I’ve been using react-set-state! to get around this by bypassing om.next’s render loop altogether, but I’m wondering if there’s a better way.

anmonteiro20:02:15

@levitanong (.forceUpdate this) could potentially work

anmonteiro20:02:23

this being the component instance

levitanong20:02:50

@anmonteiro I tried it, but it didn’t work 😞 I’m guessing it tries to update before the parser can get around to it?

levitanong20:02:23

I’d try to run (.forceUpdate this) inside the mutation, but i don’t think i have access to the component instance from a mutation fn

anmonteiro20:02:24

hrm, there's definitely a :component key in the parser if you transact! from a component

levitanong20:02:08

@anmonteiro will give that a go

levitanong20:02:04

and i don’t suppose schedule-render! would work 😛

levitanong20:02:51

and i’ve taken a look at their flush: https://github.com/reagent-project/reagent/blob/v0.6.0/src/reagent/impl/batching.cljs#L91 At this point I can’t understand what’s going on anymore 😛

anmonteiro20:02:33

@levitanong I'm afraid I don't have substantial React Native experience to help you any further

levitanong20:02:53

thanks anyway, @anmonteiro 🙂

sova-soars-the-sora23:02:35

@levitanong (om/transact! ..) takes 2 args, one is a component and the rest can be mutates_and_keys_to_be_re-read ... I just figured that out yesterday, it may be germane to what you're doing.