Binding to a computed property that depends on state set up in init will fail. This impacts relationships in Ember Data (which depend on the stateManager set up in init).
See http://stackoverflow.com/questions/14361760/binding-to-relationship-property for the original report
This is related to stuff @kselden is working on.
See also emberjs/data#708.
Does this mean I also cannot create a property that listens for changes in a belongsTo field? I'm having this problem right now and I'm not sure if this issue here is the cause.
This seems really bad. After updating to master im seeing computed properties being called before init.
@ghempton Were you not seeing this previously? It's been this way for a while.
This works fine for us using a build that was 25 days old
@ghempton Is there any possibility of you running a git bisect to figure out what commit causes the change?
Inactive and less of an issue than it used to be, if an issue at all.