From 270321b5dcd1108437dc91b1e582230402b1718a Mon Sep 17 00:00:00 2001 From: Rik Date: Fri, 22 Jun 2018 04:31:37 +0200 Subject: [PATCH] docs: call correct changes function (#1921) --- docs/reference/slate/change.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/slate/change.md b/docs/reference/slate/change.md index 48369ed04..f9e91d6ec 100644 --- a/docs/reference/slate/change.md +++ b/docs/reference/slate/change.md @@ -99,7 +99,7 @@ Set the entire `value` using either a `properties` object or a `Value` object. C Warning: Calling `setValue` with a `Value` object has unpredictable behavior including the loss of the edit history. Only use with a `Value` object if you know what you are doing. For most use cases, we recommend passing `properties` as an `Object` (e.g. `change.setValue({data: myNewDataObject})`. -Hint: Wrapping the call to `setValue` as follows can be helpful if you want to update a value, like in the value's `data` but do not want to have another save point in the undo history: `change.setOperationFlag({save: false}).change({data: myNewDataObject}).setOperationFlag({save: true}). +Hint: Wrapping the call to `setValue` as follows can be helpful if you want to update a value, like in the value's `data` but do not want to have another save point in the undo history: `change.setOperationFlag({save: false}).setValue({data: myNewDataObject}).setOperationFlag({save: true}). ## Current Value Changes