Avoid eager cache refresh after insert and remove (#13334)

By doing the cache coverage check lazily, multiple inserts or removes
happening "at the same time" can be taken into account when deciding
which rows to fetch. 

Change-Id: I25c8248a1ec4cae76484c959efd474c9a880d329

1 files changed, 2 insertions, 2 deletions

diff --git a/client/src/com/vaadin/client/data/AbstractRemoteDataSource.java b/client/src/com/vaadin/client/data/AbstractRemoteDataSource.java
index 531c40e2db..7546ac6054 100644
--- a/client/src/com/vaadin/client/data/AbstractRemoteDataSource.java
+++ b/client/src/com/vaadin/client/data/AbstractRemoteDataSource.java
@@ -429,7 +429,7 @@ public abstract class AbstractRemoteDataSource<T> implements DataSource<T> {
 
         assertDataChangeHandlerIsInjected();
         dataChangeHandler.dataRemoved(firstRowIndex, count);
-        checkCacheCoverage();
+        ensureCoverageCheck();
 
         Profiler.leave("AbstractRemoteDataSource.removeRowData");
     }
@@ -476,7 +476,7 @@ public abstract class AbstractRemoteDataSource<T> implements DataSource<T> {
 
         assertDataChangeHandlerIsInjected();
         dataChangeHandler.dataAdded(firstRowIndex, count);
-        checkCacheCoverage();
+        ensureCoverageCheck();
 
         Profiler.leave("AbstractRemoteDataSource.insertRowData");
     }