Fork me on GitHub
#re-frame
<
2020-01-17
>
mccraigmccraig16:01:04

anyone know when the 0.11.0 release is likely to drop ? i'd quite like the error boundaries...

kenny16:01:58

Is there something new in 0.11.0 with regards to error boundaries? We have been using error boundaries in re-frame 0.10.9 for a while now.

mccraigmccraig16:01:43

oh, i thought they only came with reagent-0.9... and re-frame-0.11.0 is the first release with that reagent

kenny16:01:17

I think it's related to the version of react you're running.

kenny16:01:42

We're running reagent 0.8.1 and react 16.8.6

mccraigmccraig16:01:47

which told me reagent-0.9

mccraigmccraig16:01:45

are you using those lifecycle methods via reagent, or doing something different ?

kenny16:01:53

Huh, weird. We're using :component-did-catch so I know that works.

kenny16:01:09

Yes, via reagent.

mccraigmccraig16:01:11

so maybe it was just beta until 0.9.0 or something

mccraigmccraig16:01:52

either way, looks like i can use error-boundaries right now, and i should believe docs even less than i already do!

kenny16:01:14

Haha. Looks like there may not be a :get-derived-state-from-error. We have only been using :component-did-catch with no issues.

mccraigmccraig17:01:33

i guess :get-derived-state-from-error isn't really necessary

mccraigmccraig17:01:40

at least in a re-frame app

superstructor00:01:40

Re release re-frame 0.11.0-rc4 will become 0.11.0 unless any major issues are reported. It includes reagent 0.9.1

superstructor00:01:59

You don't necessarily need get-derived-state-from-error to use error boundaries but that is available from reagent 0.9.x and reframe 0.11.x