dot notation vs Ember.get behavior shift in Ember 3.2 from Ember 3.1.1

This issue manifests in Ember 3.2 but not Ember 3.1.1

Imagine you have an instance of an Ember.Object (maybe a service), and on this instance you have an instance of another Ember.Object (perhaps a model), and this model has a property.

If model is isDestroyed: true, then the following occurs regardless of the value of property (e.g. it could be a computed, an ES getter, a simple boolean), the following behavior divergence below is observed.

service.get('model.prop'); // undefined
service.model.prop; // a value

Additionally, if prop has dependent keys, then the first call will error that you cannot set dependent keys, while subsequent calls will work.

service.model.prop; // throws error
service.model.prop; // a value

[Exelord]

It’s still valid case 😕

[rwjblue]

Parts of it are definitely still valid, though I don’t know that we are likely to change much fundamentally here.

I suspect the underlying issue is that once destroyed we won’t actually compute computeds, we will generally only return a previously cached value (if it had been retrieved before).