Defining properties on your model class breaks the link to Firebase

[balinterdi]

When model classes are defined in Ember, its properties are listed with their initial values:

App.User = EmberFire.Object.extend({
  username: '',
  votesLeft: 10
})

Since emberFire relies on missing property lookups on the model object (EmberFire.Object) to be proxied to Firebase, if one defines the properties thusly, emberFire will stop working because the property lookups do not get propagated to Firebase.

I'm not sure how much of a problem this is. I'm sure this will bite several Ember devs when starting to use Firebase and I also think the above definition of properties is pretty handy to see what properties a model class has.

I jotted this down to hear your opinion and to see if there is a way around this.

[NedgoIO]

I would also like to hear the firebase team's opinion on this.

[anantn]

We discussed this a while ago, we'll be looking into alternatives such as:
a) Detecting when a developer sets properties like this and logging a message
b) Using hasOwnProperty and including manually set properties in the remote data (this is trickier, especially if we want to be compatible with older browsers re: detecting when the properties change).

[aputinski]

@balinterdi @ogdenit We're releasing v0.2.0 which is designed to work directly with Ember Data, so I'm going to close this issue for now because v0.1.0 will no longer be officially supported