title: Ember Data deleteRecord() followed by rollback() - how to make object reappear in list?
body: <p>In a controller:</p>
  
  <pre><code>    actions: {
  
          selectDelete: function(note) {
              console.log('selectDelete', note);
              note.deleteRecord();
              note.save().then(
                  function success() {
                      console.log('Deleted successfully');
                  }, function failure() {
                      console.log('Delete error before',
                        this.get('isDeleted'), this.get('isDirty'); //true, true
                      // note.transitionTo('loaded.saved'); //also has same effect
                      note.rollback();
                      console.log('Delete error after',
                        this.get('isDeleted'), this.get('isDirty'); //false, false
                  }
              );
          },
      }
  </code></pre>
  
  <p>In a template:</p>
  
  <pre><code>{{#each note in model.notes}}
  &lt;li&gt;
      &lt;span&gt;{{note.text}}&lt;/span&gt;
      &lt;span {{action 'selectDelete' note}}&gt;[Delete]&lt;/span&gt;
  &lt;/li&gt;
  {{else}}
  No Notes
  {{/each}}
  </code></pre>
  
  <p>Now when I click on the <code>[Delete]</code> span, the <code>selectDelete</code> action gets triggered, with the following output:</p>
  
  <pre><code>Delete error before true true
  Delete error after false false
  </code></pre>
  
  <p>... which means that the rollback was successful, and the record has indeed been un-deleted.</p>
  
  <p>However, while calling <code>deleteRecord()</code> updates the DOM to remove the part that represents the deleted record,
  calling <code>rollback()</code> appears to revert the changes to the record in memory, but fails to revert the changes in the DOM.</p>
  
  <p>How can I ensure that <code>rollback()</code> triggers this change?</p>
  
  <p>Alternatively, is there a way to alter the default behaviour such that <code>deleteRecord()</code> does not trigger a change in the DOM,
  and instead leaves it unchanged, deferring that change until the <code>success</code> callback is called?
  (That way a reverting changes to the DOM will not be necessary)</p>