`oncreate` vs `onupdate`

I noticed that onupdate doesn’t fire during the first update, is this intentional?

I think, in most systems that offer both a create and update notification, the initial creation triggers both a create and an update notification, because there isn’t typically much use for an update notification that doesn’t fire the first time.

Typically the notifications you need are for creation, for destruction, or for all updates - rarely does anyone need a notification for “all updates except the first one”.

Thoughts?

[mindplay-dk]

By no means “there” yet, and I have to quit for today, but I did make some interesting progress.

https://jsfiddle.net/mindplay/o2rdL259/4/

I’ve extended the h function so I can test if type is a constructor that extends Component - right now it’s recreating the component on every iteration, but so far so good. Next step is to try to inject the component instance into a reserved field in props, and make it carry over via oldProps, which should be possible by proxying oncreate and onupdate.

The sample class here illustrates what I’m trying to do - I think that class-based components do make sense here - you’d be able to encapsulate the model and the render function into a self-sufficient, reusable component. It’s not exactly the React approach, as I’m putting the component itself in charge of managing it’s own state and calling Component.invalidate() to re-render. We’ll see if this pans out… 😃

[jorgebucaran]

Or we could leave things the way they are.