createRecord with an existing ID overrides the record about emberfire

[aputinski]

@mutewinter can you please post a more detailed example? store.createRecord() shouldn't send any data to Firebase without calling save() on the record

[mutewinter]

Ah, that's correct. I also meant to include the save() call in there.

My thought is that most APIs would throw an error if an ID were specified that already existed on create.

[aputinski]

@mutewinter sure thing. I think that the dematerializeRecord() fix in the other issue you posted should fix this as well, but I'll throw an error just in case.

[aputinski]

@mutewinter I think this is where security rules come into play. EmberFire isn't going to check if data exists at a location, but it will throw an error if the write fails — so if a security rule was set up like this:

{
  "posts": {
    "$post": {
      ".write": "!data.exists()"
    }
  }
}

post.save() would fail and EmberFire would throw an error.

[mutewinter]

Ah, that's a really good point. It's definitely a server concern. And in this case, the rules.json is the server.