they added another one??? jeez

how many lifecycle methods do we need?

@claudiu Is your PR done?

@tony.kay code is working, still need to update doc/book with new default method.

ok

this lifecycle seems like a pretty good idea IMO, good way to handle error is render

I mean they already had componentDidCatch, which can side effect (and set state)…they added this and deprecated the other one

prob didn’t work right to side-effect in CDC for some internal reason

but this new one breaks Fulcro’s state model that is on top of Reacts 😞

yeah but the problem is you often don’t want to set-state when an exceptions happens you just want to show an alternative UI, but if the user does something that “fixes” the UI you want to now show the actual UI (rather than the alternative)

so if you wan to use did-catch for that you also need a did-not-throw to unset the state

I know tony has a bunch of tutorial videos that deal with individual topics, but if I have a bunch of angular guys asking for a video that showcases fulcro and in particularly the reloaded workflow, which video do you suggest?

I don’t know about a video like that, but you could clone the demo app and demo that live?