It's not guaranteed to work consistently. When using a template like this:
{{model.prop}}
it relies on observing 'model.prop'
. While it may function in some instances, it can lead to unexpected results or strange messages from Ember.
At the core of Ember lies its object model, which serves as the foundation for managing objects and handling properties within the framework. Embracing Ember means embracing this object model, rooted in traditional inheritance principles.
An issue commonly arises when a server API returns a plain JavaScript object as a model property value. If you need to manipulate the object or display its properties in templates, it's advisable to either convert the object into an Ember Object (typically achieved through transforms) or utilize embedded models. The latter option can be complex and may necessitate adjustments on the server side, such as incorporating an ID in the embedded models. I personally opted for the latter approach and found it crucial for maintaining my sanity.