lifecycle method onChange called before onInit and onCheck

I have attached onInit, onCheck, onChange, and onAllChangesDone lifecycle methods attached to a component(to reason about the sequence in which these methods get called). When the component is instantiated, its onChange method is called first, then onInit, onCheck and onAllChangesDone methods are called in sequence. The docs says onChange

Notify a directive when any of its bindings have changed. This method is called right after the directive’s bindings have been checked, and before any of its children’s bindings have been checked. It is invoked only if at least one of the directive’s bindings has changed.

1. Why onChange is called initially when the component is instantiating?
2. And whenever I change the value of a property on the component, onChange is fired first before onCheck. Is this intended behavior?

Here is a simple plunker for the above question -> http://plnkr.co/edit/sk6Xi7L6a7ob9xiRJaSJ?p=preview. View the console for the sequence.

[poshest]

+1 for $onInit being called before $onChanges. I think that’s the way most people would expect it. I have many use cases for an init function which $onChanges depends on already having been called. I don’t have a single use case for the other way around. There’s consternation in the AngularJS world about it too.

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}