peekRecord() not working as expected

[denchen]

I'm having an issue with peekRecord(), and I'm hoping I'm just not understanding how it works.

Basically, I have a record that I want to destroy, but after I destroy it and then use peekRecord() on it, I still see the record. Is this expected? In essence, I'm doing this:

try {
  let record = this.store.peekRecord('my-model', 123);
  if (record) {
    yield record.destroyRecord();
    // I expect this next command to return null or Record Not Found
    let record2 = this.store.peekRecord('my-model', 123);
    console.debug('Record is still here:', record2.get('id'));
  }
} catch(e) {
  console.error('Error:', e);
}

I'm using ember-cli 2.12.3.

[hjdivad]

@denchen the deletion has not been persisted yet.

record.destroyRecord.then(() => {
  store.hasRecordForId('model-name', id);
})

[stefanpenner]

@hjdivad wouldn't the yield handle that? (Assuming the generator supports promises)

[pangratz]

The record is in the root.deleted.saved state, see this twiddle.

[runspired]

I believe this has been cleaned up, but we should confirm.

[sly7-7]

@rwjblue @bmac I can't test the previous twiddle against ember-data canary, because of this error:

ember-data.js:258 Uncaught Error: Could not find module `@ember/ordered-set` imported from `ember-data/-private/system/ordered-set`

Something wrong with the external import ? must we add something somewhere?

@runspired So I tested the twiddle against beta, and the destroyed record is still in the store. (unloadRecord works btw)

[runspired]

Closing in favor of #5006 which is a duplicate: TL;DR destroyed records are not unloaded automatically.