Fork me on GitHub
#re-frame
<
2018-12-20
>
danielneal12:12:25

If I'm in an interceptor and I want to stop the handler from ever firing in some case, what do I need to do something else apart from setting :queue to nil and :event to nil in the context. Or is this enough? My handler still seems to be firing - can't get it to stop!

Whiskas20:12:23

Guys, my re-frame-10x arrows stopped working

Whiskas20:12:53

I click on the arrows to expand the db and nothing happens

Whiskas20:12:00

someone had this problem all of asudden?

Whiskas20:12:24

i’m referring to the expansion-button

Whiskas20:12:10

i did a factory reset and it is working again now

mikethompson20:12:45

@mateus.pimentel.w Hmm. When I've seen this problem before its been because there's a mixture of React versions. Make sure you are using the version of re-frame-10x to match the version of React used in your app

Whiskas20:12:20

I hope i’m not loading any other react instance hah

Whiskas20:12:34

but it’s probably what is happening

Whiskas20:12:52

Because i’m mixing JSX with Reagent

mikethompson20:12:21

Your use of Reagent in your app will be pulling in a particular version of React.

mikethompson20:12:45

And there are two versions of re-frame-10xdepending on which version of React you are using (15 or 16)

Whiskas20:12:01

got it, i will look at this, ty

Whiskas20:12:49

my package.json is using react-16 and my re-frame-10x is for react 15

Whiskas20:12:22

reagent is probabbly using react 15

Whiskas20:12:29

i will see how to align these things together

danielneal20:12:48

@mikethompson Thanks! Good to know that is correct approach. Problem between keyboard and chair - I was setting :coeffects :queue to nil!