title: Why does react-admin call getOne after delete, on the deleted object, in optimistic rendering mode?
body: <p>We see that as soon as we call a 'delete' operation on the data provider, that react-admin pushes a CRUD_GET_ONE action onto the <code>optimisticCalls</code> array in <code>usedataProvider</code>.</p>
  <p>Then after the server response on the delete operation, this is replayed and a <code>getOne</code> request is issued for the meanwhile deleted record. This causes a rejected promise from the data provider (since the object is not found) which shows as an 'element not found' popup in react-admin UI.</p>
  <p>We see this both with <code>undoable</code> set to true or false, and with a <code>redirect=list</code> (the pop-up shows after redirection to list page upon delete)</p>
  <p><em><strong>Why is there a <code>CRUD_GET_ONE</code> action dispatched upon pressing <code>&lt;DeleteButton&gt;</code> that gets buffered and executed after the server has deleted the object? How can we avoid the issue?</strong></em></p>
  <p>Note this comment in <code>useDataProvider.ts</code> which explains why <code>getOne</code> gets executed after server response, but why is the action dispatched in the first place?</p>
  <pre><code>// in optimistic mode, all fetch calls are stacked, to be
  // executed once the dataProvider leaves optimistic mode.
  // In the meantime, the admin uses data from the store.
  </code></pre>