@trackunit/react-table 2.11.5 → 2.11.7-alpha-85fb68bb35f.0

package/index.cjs.js

@@ -569,6 +569,14 @@ const isOwnedByCurrentUser = (ownerId, clientSideUserId) => ownerId === undefine
  * write — their storage changes only when they edit the table. Switching
  * back to the opener does not write the hash that is on screen then.
  *
+ * A layout that exists only in localStorage is not copied into the hash on
+ * load. Doing that put the current layout into every history entry, so a
+ * later visit via history, a bookmark, or a login redirect replayed an
+ * older layout and saved it over the current one (GLU-2396). The hash is
+ * written when the user changes the table, replacing the current history
+ * entry, or when they open a URL that already carries one. A push per edit
+ * would leave the same replayable entries behind.
+ *
  * `onTableStateChange` takes a *partial* state and merges it into whatever
  * was reported earlier in the session, so a consumer can report a single
  * slice (e.g. only `expanded`) without the omitted fields falling back to
@@ -607,7 +615,10 @@ const useTablePersistence = (persistenceKey) => {
         validate: validateTableState,
         toUrlValue,
         fromUrlValue,
-        replace: false,
+        // Replace, so a second edit updates this visit's history entry. A push
+        // per column change left older layouts in history, and a later full load
+        // of one of them saved that layout over the newer one (GLU-2396).
+        replace: true,
         clientSideUserId,
         localStorageEnabled,
         // `toUrlValue` strips fields that should not be shareable from the URL.

package/index.esm.js

@@ -568,6 +568,14 @@ const isOwnedByCurrentUser = (ownerId, clientSideUserId) => ownerId === undefine
  * write — their storage changes only when they edit the table. Switching
  * back to the opener does not write the hash that is on screen then.
  *
+ * A layout that exists only in localStorage is not copied into the hash on
+ * load. Doing that put the current layout into every history entry, so a
+ * later visit via history, a bookmark, or a login redirect replayed an
+ * older layout and saved it over the current one (GLU-2396). The hash is
+ * written when the user changes the table, replacing the current history
+ * entry, or when they open a URL that already carries one. A push per edit
+ * would leave the same replayable entries behind.
+ *
  * `onTableStateChange` takes a *partial* state and merges it into whatever
  * was reported earlier in the session, so a consumer can report a single
  * slice (e.g. only `expanded`) without the omitted fields falling back to
@@ -606,7 +614,10 @@ const useTablePersistence = (persistenceKey) => {
         validate: validateTableState,
         toUrlValue,
         fromUrlValue,
-        replace: false,
+        // Replace, so a second edit updates this visit's history entry. A push
+        // per column change left older layouts in history, and a later full load
+        // of one of them saved that layout over the newer one (GLU-2396).
+        replace: true,
         clientSideUserId,
         localStorageEnabled,
         // `toUrlValue` strips fields that should not be shareable from the URL.

package/migrations/entry.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"entry.js","sourceRoot":"","sources":["../../../../../libs/react/table/migrations/entry.ts"],"names":[],"mappings":"","sourcesContent":["export {};\n"]}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@trackunit/react-table",
-  "version": "2.11.5",
+  "version": "2.11.7-alpha-85fb68bb35f.0",
   "repository": "https://github.com/Trackunit/manager",
   "license": "SEE LICENSE IN LICENSE.txt",
   "engines": {
@@ -11,15 +11,15 @@
     "react-dnd": "16.0.1",
     "react-dnd-html5-backend": "16.0.1",
     "tailwind-merge": "^2.0.0",
-    "@trackunit/react-components": "3.7.4",
-    "@trackunit/react-core-hooks": "1.25.3",
-    "@trackunit/shared-utils": "1.19.3",
-    "@trackunit/css-class-variance-utilities": "2.3.3",
-    "@trackunit/ui-icons": "1.17.3",
-    "@trackunit/react-table-base-components": "2.12.5",
-    "@trackunit/react-form-components": "2.10.5",
-    "@trackunit/i18n-library-translation": "2.8.3",
-    "@trackunit/iris-app-runtime-core-api": "1.21.3",
+    "@trackunit/react-components": "3.8.1-alpha-85fb68bb35f.0",
+    "@trackunit/react-core-hooks": "1.25.4-alpha-85fb68bb35f.0",
+    "@trackunit/shared-utils": "1.19.4-alpha-85fb68bb35f.0",
+    "@trackunit/css-class-variance-utilities": "2.3.4-alpha-85fb68bb35f.0",
+    "@trackunit/ui-icons": "1.17.4-alpha-85fb68bb35f.0",
+    "@trackunit/react-table-base-components": "2.12.7-alpha-85fb68bb35f.0",
+    "@trackunit/react-form-components": "2.10.7-alpha-85fb68bb35f.0",
+    "@trackunit/i18n-library-translation": "2.8.4-alpha-85fb68bb35f.0",
+    "@trackunit/iris-app-runtime-core-api": "1.21.4-alpha-85fb68bb35f.0",
     "zod": "^3.25.76"
   },
   "peerDependencies": {

package/src/hooks/useTablePersistence/useTablePersistence.d.ts

@@ -88,6 +88,14 @@ type UseTablePersistenceResult = {
  * write — their storage changes only when they edit the table. Switching
  * back to the opener does not write the hash that is on screen then.
  *
+ * A layout that exists only in localStorage is not copied into the hash on
+ * load. Doing that put the current layout into every history entry, so a
+ * later visit via history, a bookmark, or a login redirect replayed an
+ * older layout and saved it over the current one (GLU-2396). The hash is
+ * written when the user changes the table, replacing the current history
+ * entry, or when they open a URL that already carries one. A push per edit
+ * would leave the same replayable entries behind.
+ *
  * `onTableStateChange` takes a *partial* state and merges it into whatever
  * was reported earlier in the session, so a consumer can report a single
  * slice (e.g. only `expanded`) without the omitted fields falling back to