From eff85c7392909d9b2cd2925df921014501a715df Mon Sep 17 00:00:00 2001
From: dtbuild <dtbuild@rigil>
Date: Thu, 18 Apr 2024 08:55:44 +0000
Subject: [PATCH] 1c48c11ac0168d9598795641b4fc337a2233289e Fix: Don't modify
 the display array in `-api row().remove()` - it should wait for the next draw

This relates to https://github.com/DataTables/DataTablesSrc/issues/269
and is fairly nuanced - it boils down to the fact that the display array
should reflect what is shown in the table, and deleting a value from it
will cause an index offset. The other option might be to make the
element null, as happens with the master, but that would be a change in
type and I'm not certain everything could handle that. The array will
regenerate on the next draw, so it is properly in sync with what is
drawn now.

Sync to source repo @1c48c11ac0168d9598795641b4fc337a2233289e
---
 datatables.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/datatables.json b/datatables.json
index 83b3032..a6ee470 100644
--- a/datatables.json
+++ b/datatables.json
@@ -14,5 +14,5 @@
     ],
     "src-repo": "http://github.com/DataTables/DataTablesSrc",
     "last-tag": "2.0.4",
-    "last-sync": "d04853a9ab4fb7e9f5b4acfc1fea81f5952116e8"
+    "last-sync": "1c48c11ac0168d9598795641b4fc337a2233289e"
 }
\ No newline at end of file