Search first

• I searched and no similar issues were found

What Happened?

Related issues:

• [Plugin API] .insertBatchBlock: option before: false doesn't work in combination with sibling: false #10870
• [Plugin API] .insertBatchBlock: inserting block before the FIRST block in page results in unnecessary content characters #10871
• [Plugin API] .insertBatchBlock continues numbering, when no such property was provided: #10967

Demo

Reproduce the Bug

1. Create some block with any content
2. Create another block under the first one (as sibling) with content "block after"
3. Copy the UUID of the first block
4. Insert it to the API call (replacing the text "INSERT UUID HERE") and execute it:

   logseq.api.insert_batch_block('INSERT UUID HERE', {content: 'A', properties: {id: '471b3419-3479-40b8-a84c-be0a4c747165'}, children: [{content: 'B', properties: {id: "46a6eba1-57bc-4c3c-aa03-803fe56b71e8"}}, {content: 'A & B refs: ((46a6eba1-57bc-4c3c-aa03-803fe56b71e8)) ((471b3419-3479-40b8-a84c-be0a4c747165))'}]}, {sibling: true, keepUUID: true})
   

5. Result:
   • Inserted node won't appear visually (but all of them are inserted)
   • The second block "block after" became invisible (but still present in the graph)

NOTE

• This API call is the minimal example. I don't know the exact reason of this strange behaviour. Other cases I've tested works correctly. This is the BAD one.

Expected Behavior

Normal API work and visibility of all blocks.

Desktop or Mobile Platform Information

MacOS v14.5
Logseq Desktop v0.10.9