From b6614700bbee5566f4d5897fcb689071e6df888e Mon Sep 17 00:00:00 2001 From: realvirtu <103977942+realvirtu@users.noreply.github.com> Date: Wed, 5 Aug 2026 12:49:02 -0400 Subject: [PATCH] Remove "value" null check from song variation merging --- assets/content/cookbook/Introduction/05.AppendingAndMerge.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/assets/content/cookbook/Introduction/05.AppendingAndMerge.md b/assets/content/cookbook/Introduction/05.AppendingAndMerge.md index 558a35ad..b85f1d9d 100644 --- a/assets/content/cookbook/Introduction/05.AppendingAndMerge.md +++ b/assets/content/cookbook/Introduction/05.AppendingAndMerge.md @@ -228,9 +228,7 @@ Enter the `inverse` property, and the `test` operation: [ // If `songVariations` does not have a given value, then the next patch gets triggered. // Our operation below works the same as `test`, but in reverse, hence the name `inverse`. - // - // Basically, if `songVariations` is not `value`, then the next patches will be rejected. - {"op": "test", "path": "/playData/songVariations", "value": null, "inverse": true}, + {"op": "test", "path": "/playData/songVariations", "inverse": true}, // Set `songVariations` to []. {"op": "add", "path": "/playData/songVariations", "value": []}