[update] what's new for v9.2 and docs for new grid modules

mafanya23 · mafanya23 · commit 5adfe0dcc81e · 2025-06-19T17:05:02.000+03:00
diff --git a/docs/grid/api/grid_blockselection_config.md b/docs/grid/api/grid_blockselection_config.md
@@ -10,7 +10,7 @@ description: You can explore the blockSelection config of Grid in the documentat
 This functionality requires PRO version of the DHTMLX Grid (or DHTMLX Suite) package.
 :::
 
-@short: Optional. Enables/disables block selection management within a grid
+@short: Optional. Enables/disables the BlockSelection module during the Grid initialization
 
 ### Usage
 
diff --git a/docs/grid/api/grid_clipboard_config.md b/docs/grid/api/grid_clipboard_config.md
@@ -10,7 +10,7 @@ description: You can explore the clipboard config of Grid in the documentation o
 This functionality requires PRO version of the DHTMLX Grid (or DHTMLX Suite) package.
 :::
 
-@short: Optional. Enables/disables the [`Clipboard`](grid/usage_clipboard.md) module within a grid
+@short: Optional. Enables/disables the Clipboard module during the Grid initialization
 
 :::note
 The module requires the [`RangeSelection`](grid/usage_rangeselection.md) module to be enabled and is best used in conjunction with the [`BlockSelection`](grid/usage_blockselection.md) module in the `"range"` mode (enabled on initialization of the `Clipboard` module) for convenient range selection via the UI.
@@ -74,8 +74,8 @@ const grid = new dhx.Grid("grid_container", {
 });
 ~~~
 
-**Related article:** [Clipboard](grid/configuration.md/#clipboard)
-
 **Related sample**: [Grid. Clipboard. Financial data with formatted copy/paste](https://snippet.dhtmlx.com/1fnkhwm0)
 
+**Related article:** [Clipboard](grid/configuration.md/#clipboard)
+
 @changelog: added in v9.2
diff --git a/docs/grid/api/grid_dragpanel_config.md b/docs/grid/api/grid_dragpanel_config.md
@@ -10,7 +10,7 @@ description: You can explore the dragPanel config of Grid in the documentation o
 This functionality requires PRO version of the DHTMLX Grid (or DHTMLX Suite) package.
 :::
 
-@short: Optional. Enables/disables the [`dragPanel`](grid/usage_dragpanel.md) module within a grid
+@short: Optional. Enables/disables the DragPanel module during the Grid initialization
 
 ### Usage
 
@@ -27,7 +27,7 @@ dragPanel?:
 @default: false
 
 :::note
-The module is automatically enabled, if the row Drag-and-Drop is active (e.g., `dragItem: "row"` or `dragItem: "both"`), and either the [`BlockSelection`](grid/usage_blockselection.md) or [`Clipboard`](grid/usage_clipboard.md) modules are enabled.
+The module is automatically enabled, if the [row Drag-and-Drop](grid/configuration.md/#drag-n-drop) functionality is active (e.g. via the `dragItem: "row"` or `dragItem: "both"` properties), and either the [`BlockSelection`](grid/usage_blockselection.md) or [`Clipboard`](grid/usage_clipboard.md) modules are enabled.
 :::
 
 @example:
@@ -85,8 +85,9 @@ const grid = new dhx.Grid("grid_container", {
 </script>
 ~~~
 
+**Related sample:** [Grid. DragPanel. Initialization](https://snippet.dhtmlx.com/oyk02cr6)
+
 **Related article:** [Using the DragPanel module](grid/configuration.md/#using-the-dragpanel-module)
 
-**Related sample:** [Grid. DragPanel. Initialization](https://snippet.dhtmlx.com/oyk02cr6)
 
 @changelog: added in v9.2
diff --git a/docs/grid/api/grid_history_config.md b/docs/grid/api/grid_history_config.md
@@ -10,7 +10,7 @@ description: You can explore the history config of Grid in the documentation of
 This functionality requires PRO version of the DHTMLX Grid (or DHTMLX Suite) package.
 :::
 
-@short: Optional. Enables/disables the `History` module during the Grid initialization
+@short: Optional. Enables/disables the History module during the Grid initialization
 
 ### Usage
 
@@ -66,6 +66,8 @@ const grid = new dhx.Grid("grid_container", {
 grid.history.enable(); // enabling the module
 ~~~
 
+**Related sample:** [Grid. History. Configuration](https://snippet.dhtmlx.com/m88562wf)
+
 **Related article:** [History of Grid actions](grid/configuration.md/#history-of-grid-actions)
 
 @changelog: added in v9.2
diff --git a/docs/grid/api/grid_rangeselection_config.md b/docs/grid/api/grid_rangeselection_config.md
@@ -10,7 +10,7 @@ description: You can explore the rangeSelection config of Grid in the documentat
 This functionality requires PRO version of the DHTMLX Grid (or DHTMLX Suite) package.
 :::
 
-@short: Optional. Enables/disables range selection management within a grid
+@short: Optional. Enables/disables the RangeSelection module during the Grid initialization
 
 ### Usage
 
diff --git a/docs/grid/api/history/add_method.md b/docs/grid/api/history/add_method.md
@@ -6,7 +6,7 @@ description: You can explore the add method of Grid history in the documentation
 
 # add()
 
-@short: adds a new action to the history
+@short: adds a new action into the history of actions within the Grid
 
 ### Usage
 
@@ -17,7 +17,6 @@ interface IAction {
     type: ActionType; 
     batch: IRow[];
     inverse?: IAction; 
-    timestamp?: number; 
 }
 
 add(action: IAction): void;
@@ -29,14 +28,13 @@ add(action: IAction): void;
     - `type: ActionType` - the type of action: "add", "remove", "removeAll", or "change"
     - `batch: IRow[]` - an array of rows representing the data affected by the action (e.g., added, removed, or modified rows)
     - `inverse?: IAction` - the inverse action required for undoing (mandatory for the "change" and "removeAll" types, not required for other types)
-    - `timestamp?: number` - the timestamp of the action in milliseconds (set automatically, if not provided)
 
 :::note
-The `action` argument must conform to the `IAction` interface. If the module is disabled, the action type is invalid, or the `inverse` property is missing for a `change` action, the [`error`](grid/api/history/error_event.md) event is triggered. The `timestamp` field is automatically added if not specified.
+The `action` argument must conform to the `IAction` interface. If the module is disabled, the action type is invalid, or the `inverse` property is missing (for actions with the "change" and "removeAll" types), the [`error`](grid/api/history/error_event.md) event is triggered. 
 :::
 
 @example:
-// The example shows adding a new row via `DataCollection` with an explicitly specified timestamp
+// The example shows adding a new row via `DataCollection` 
 const grid = new dhx.Grid("grid_container", {
     columns: [
         { id: "name", header: [{ text: "Name" }] },
@@ -52,7 +50,7 @@ const grid = new dhx.Grid("grid_container", {
 const newItem = { id: "2", name: "New Item", value: 20 };
 grid.data.add(newItem);
 
-// recording the action in the history with a timestamp
+// recording the action in the history 
 grid.history.add({
     type: "add",
     batch: [{ ...newItem }],
diff --git a/docs/grid/api/history/afteradd_event.md b/docs/grid/api/history/afteradd_event.md
@@ -6,7 +6,7 @@ description: You can explore the afterAdd event of Grid history in the documenta
 
 # afterAdd
 
-@short: triggered before adding an action to the history
+@short: triggered after successfully adding an action to the history
 
 @signature: {'afterAdd: (action: IAction) => void;'}
 
@@ -15,8 +15,7 @@ The callback of the event is called with the following parameters:
 - `action: IAction` - the object of the added action containing:
     - `type: ActionType` - the type of action: "add", "remove", "removeAll", or "change"
     - `batch: IRow[]` - an array of rows representing the data affected by the action (e.g., added, removed, or modified rows)
-    - `inverse?: IAction` - the inverse action required for undoing (mandatory for the "change" and "removeAll" types, not required for other types)
-    - `timestamp?: number` - the timestamp of the action in milliseconds (set automatically, if not provided)
+    - `inverse?: IAction` - the inverse action required for undoing (for the "change" and "removeAll" types)
 
 @example:
 const grid = new dhx.Grid("grid_container", {
@@ -36,6 +35,8 @@ grid.history.events.on("afterAdd", (action) => {
 
 @descr:
 
+**Related sample:** [Grid. History. Configuration](https://snippet.dhtmlx.com/m88562wf)
+
 **Related article**: [Adding/removing Grid history actions](grid/usage_history.md/#addingremoving-grid-history-actions)
 
 **Related API**: [`add()`](grid/api/history/add_method.md), [`beforeAdd()`](grid/api/history/beforeadd_event.md)
diff --git a/docs/grid/api/history/afterredo_event.md b/docs/grid/api/history/afterredo_event.md
@@ -15,8 +15,7 @@ The callback of the event is called with the following parameters:
 - `action: IAction` - the object of the executed action containing:
     - `type: ActionType` - the type of action: "add", "remove", "removeAll", or "change"
     - `batch: IRow[]` - an array of rows representing the data affected by the action (e.g., added, removed, or modified rows)
-    - `inverse?: IAction` - the inverse action required for undoing (mandatory for the "change" and "removeAll" types, not required for other types)
-    - `timestamp?: number` - the timestamp of the action in milliseconds (set automatically, if not provided)
+    - `inverse?: IAction` - the inverse action required for undoing (for the "change" and "removeAll" types)
 
 @example:
 const grid = new dhx.Grid("grid_container", {
@@ -36,6 +35,8 @@ grid.history.events.on("afterRedo", (action) => {
 
 @descr:
 
+**Related sample:** [Grid. History. Configuration](https://snippet.dhtmlx.com/m88562wf)
+
 **Related article**: [Applying undo/redo operations to Grid history actions](grid/usage_history.md/#applying-undoredo-operations-to-grid-history-actions)
 
 **Related API**: [`redo()`](grid/api/history/redo_method.md), [`beforeRedo()`](grid/api/history/beforeredo_event.md)
diff --git a/docs/grid/api/history/afterundo_event.md b/docs/grid/api/history/afterundo_event.md
@@ -15,8 +15,7 @@ The callback of the event is called with the following parameters:
 - `action: IAction` - the object of the executed action containing:
     - `type: ActionType` - the type of action: "add", "remove", "removeAll", or "change"
     - `batch: IRow[]` - an array of rows representing the data affected by the action (e.g., added, removed, or modified rows)
-    - `inverse?: IAction` - the inverse action required for undoing (mandatory for the "change" and "removeAll" types, not required for other types)
-    - `timestamp?: number` - the timestamp of the action in milliseconds (set automatically, if not provided)
+    - `inverse?: IAction` - the inverse action required for undoing (for the "change" and "removeAll" types)
 
 @example:
 const grid = new dhx.Grid("grid_container", {
@@ -36,6 +35,8 @@ grid.history.events.on("afterUndo", (action) => {
 
 @descr:
 
+**Related sample:** [Grid. History. Configuration](https://snippet.dhtmlx.com/m88562wf)
+
 **Related article**: [Applying undo/redo operations to Grid history actions](grid/usage_history.md/#applying-undoredo-operations-to-grid-history-actions)
 
 **Related API**: [`undo()`](grid/api/history/undo_method.md), [`beforeUndo()`](grid/api/history/beforeundo_event.md)
diff --git a/docs/grid/api/history/beforeadd_event.md b/docs/grid/api/history/beforeadd_event.md
@@ -15,11 +15,10 @@ The callback of the event is called with the following parameters:
 - `action: IAction` - the action object to be added containing:
     - `type: ActionType` - the type of action: "add", "remove", "removeAll", or "change"
     - `batch: IRow[]` - an array of rows representing the data affected by the action (e.g., added, removed, or modified rows)
-    - `inverse?: IAction` - the inverse action required for undoing (mandatory for the "change" and "removeAll" types, not required for other types)
-    - `timestamp?: number` - the timestamp of the action in milliseconds (set automatically, if not provided)
+    - `inverse?: IAction` - the inverse action required for undoing (for the "change" and "removeAll" types)
 
 @returns:
-Returning `false` cancels the addition.
+Returning `false` cancels the operation.
 
 @example:
 const grid = new dhx.Grid("grid_container", {
diff --git a/docs/grid/api/history/beforeredo_event.md b/docs/grid/api/history/beforeredo_event.md
@@ -15,8 +15,7 @@ The callback of the event is called with the following parameters:
 - `action: IAction` - the action object from the redo stack containing:
     - `type: ActionType` - the type of action: "add", "remove", "removeAll", or "change"
     - `batch: IRow[]` - an array of rows representing the data affected by the action (e.g., added, removed, or modified rows)
-    - `inverse?: IAction` - the inverse action required for undoing (mandatory for the "change" and "removeAll" types, not required for other types)
-    - `timestamp?: number` - the timestamp of the action in milliseconds (set automatically, if not provided)
+    - `inverse?: IAction` - the inverse action required for undoing (for the "change" and "removeAll" types)
 
 @returns:
 Returning `false` cancels the operation.
diff --git a/docs/grid/api/history/beforeundo_event.md b/docs/grid/api/history/beforeundo_event.md
@@ -15,7 +15,7 @@ The callback of the event is called with the following parameters:
 - `action: IAction` - the action object containing:
     - `type: ActionType` - the type of action: "add", "remove", "removeAll", or "change"
     - `batch: IRow[]` - an array of rows representing the data affected by the action (e.g., added, removed, or modified rows)
-    - `inverse?: IAction` - the inverse action required for undoing (mandatory for the "change" and "removeAll" types, not required for other types)
+    - `inverse?: IAction` - the inverse action required for undoing (for the "change" and "removeAll" types)
 
 @returns:
 Returning `false` cancels the operation.
diff --git a/docs/grid/api/history/canredo_method.md b/docs/grid/api/history/canredo_method.md
@@ -6,7 +6,7 @@ description: You can explore the canRedo method of Grid history in the documenta
 
 # canRedo()
 
-@short: checks whether an action can be redone
+@short: checks whether an action within the Grid history can be redone
 
 @signature: {'canRedo(): boolean;'}
 
diff --git a/docs/grid/api/history/canundo_method.md b/docs/grid/api/history/canundo_method.md
@@ -6,7 +6,7 @@ description: You can explore the canUndo method of Grid history in the documenta
 
 # canUndo()
 
-@short: checks whether an action can be undone
+@short: checks whether an action within the Grid history can be undone
 
 @signature: {'canUndo(): boolean;'}
 
diff --git a/docs/grid/api/history/disable_method.md b/docs/grid/api/history/disable_method.md
@@ -6,7 +6,7 @@ description: You can explore the disable method of Grid history in the documenta
 
 # disable()
 
-@short: disables the module, preventing the addition of new actions to the history and the execution of any operations
+@short: disables the module, preventing the addition of new actions to the Grid history and the execution of any operations
 
 @signature: {'disable(): void;'}
 
diff --git a/docs/grid/api/history/enable_method.md b/docs/grid/api/history/enable_method.md
@@ -6,11 +6,12 @@ description: You can explore the enable method of Grid history in the documentat
 
 # enable()
 
-@short: enables the module, allowing the addition of new actions to the history
+@short: enables the module, allowing the addition of new actions to the Grid history
 
 @signature: {'enable(): void;'}
 
 @example:
+// The example shows how the module is enabled after deactivation on initialization
 const grid = new dhx.Grid("grid_container", {
     columns: [
         { id: "name", header: [{ text: "Name" }] },
diff --git a/docs/grid/api/history/error_event.md b/docs/grid/api/history/error_event.md
@@ -9,7 +9,7 @@ description: You can explore the error event of Grid history in the documentatio
 @short: triggered when an error occurs
 
 :::note
-The event is triggered when an error occurs, such as the module is disabled, the history is empty, the action type is invalid, the inverse action is missing for `undo`
+The event is triggered when an error occurs, such as the module is disabled, the history is empty, the action type is invalid, or the inverse action is missing for the `undo` operation.
 :::
 
 @signature: {'error: (error: string, action: IAction | null) => void;'}
@@ -20,9 +20,8 @@ The callback of the event is called with the following parameters:
 - `action: IAction` - the action object associated with the error, or `null`. The `action` object contains the following properties:
     - `type: ActionType` - the type of action: "add", "remove", "removeAll", or "change"
     - `batch: IRow[]` - an array of rows representing the data affected by the action (e.g., added, removed, or modified rows)
-    - `inverse?: IAction` - the inverse action required for undoing (mandatory for the "change" and "removeAll" types, not required for other types)
-    - `timestamp?: number` - the timestamp of the action in milliseconds (set automatically, if not provided)
-
+    - `inverse?: IAction` - the inverse action required for undoing (for the "change" and "removeAll" types)
+    
 @example:
 const grid = new dhx.Grid("grid_container", {
     columns: [
diff --git a/docs/grid/api/history/gethistory_method.md b/docs/grid/api/history/gethistory_method.md
@@ -6,7 +6,7 @@ description: You can explore the getHistory method of Grid history in the docume
 
 # getHistory()
 
-@short: returns a copy of the array of all actions in the history to prevent accidental modification of the internal structure
+@short: returns a copy of the array of all actions in the Grid history to prevent accidental modification of the internal structure
 
 @signature: {'getHistory(): IAction[];'}
 
@@ -15,10 +15,9 @@ Returns a copy of the array of all actions in the history. Each `action` object
     - `type: ActionType` - the type of action: "add", "remove", "removeAll", or "change"
     - `batch: IRow[]` - an array of rows representing the data affected by the action (e.g., added, removed, or modified rows)
     - `inverse?: IAction` - the inverse action required for undoing 
-    - `timestamp?: number` - the timestamp of the action in milliseconds 
 
 @example:
-// The example shows retrieving the history with timestamps
+// The example shows retrieving the history
 const grid = new dhx.Grid("grid_container", {
     columns: [
         { id: "name", header: [{ text: "Name" }] },
diff --git a/docs/grid/api/history/isdisabled_method.md b/docs/grid/api/history/isdisabled_method.md
@@ -6,7 +6,7 @@ description: You can explore the isDisabled method of Grid history in the docume
 
 # isDisabled()
 
-@short: checks whether the module is disabled
+@short: returns the module's current state
 
 @signature: {'isDisabled(): boolean;'}
 
diff --git a/docs/grid/api/history/redo_method.md b/docs/grid/api/history/redo_method.md
@@ -6,7 +6,7 @@ description: You can explore the redo method of Grid history in the documentatio
 
 # redo()
 
-@short: redoes the last undone action
+@short: reapplies the last undone action in the Grid history
 
 :::note
 If the redo stack is empty or the module is disabled, the `error` event is triggered.
diff --git a/docs/grid/api/history/remove_method.md b/docs/grid/api/history/remove_method.md
@@ -6,10 +6,10 @@ description: You can explore the remove method of Grid history in the documentat
 
 # remove()
 
-@short: removes the last action from the history
+@short: removes the last action from the Grid history
 
 :::note
-If the history is empty or the module is disabled, the operation is ignored, and an error event is triggered (for a disabled module).
+If the history is empty or the module is disabled, the operation is ignored, and the [`error`](grid/api/history/error_event.md) event is triggered (for a disabled module).
 :::
 
 @signature: {'remove(): void;'}
diff --git a/docs/grid/api/history/removeall_method.md b/docs/grid/api/history/removeall_method.md
@@ -6,10 +6,10 @@ description: You can explore the removeAll method of Grid history in the documen
 
 # removeAll()
 
-@short: clears the entire history and the redo stack
+@short: clears the entire Grid history and the redo stack
 
 :::note
-If the module is disabled, the operation is ignored, and the `error` event is triggered.
+If the module is disabled, the operation is ignored, and the [`error`](grid/api/history/error_event.md) event is triggered.
 :::
 
 @signature: {'removeAll(): void;'}
diff --git a/docs/grid/api/history/undo_method.md b/docs/grid/api/history/undo_method.md
@@ -6,10 +6,12 @@ description: You can explore the undo method of Grid history in the documentatio
 
 # undo()
 
-@short: undoes the last action in the history by applying the inverse action (for `change`, `removeAll`) or restoring data (for `add`, `remove`)
+@short: undoes the last action in the Grid history 
+
+Depending on the type of the action, the method either applies the inverse action (for the "change" and "removeAll" types) or restores data (for the "add" and "remove" types).
 
 :::note
-If the history is empty, the module is disabled, or no inverse action is available, the `error` event is triggered.
+If the history is empty, the module is disabled, or no inverse action is available (for actions with the "change" and "removeAll" types), the [`error`](grid/api/history/error_event.md) event is triggered.
 :::
 
 @signature: {'undo(): void;'}
diff --git a/docs/grid/configuration.md b/docs/grid/configuration.md
diff --git a/docs/grid/usage_blockselection.md b/docs/grid/usage_blockselection.md
diff --git a/docs/grid/usage_clipboard.md b/docs/grid/usage_clipboard.md
diff --git a/docs/grid/usage_dragpanel.md b/docs/grid/usage_dragpanel.md
diff --git a/docs/grid/usage_history.md b/docs/grid/usage_history.md
diff --git a/docs/whatsnew.md b/docs/whatsnew.md
