[Feature] Embed blocks from query or Dataview output

[parkeraddison]

Current Behavior

Currently, Sync Embed supports standard Obsidian transclusion targets (files or heading sections within files).

Requested Behavior

It would be amazing if somehow the output of a Obsidian query

```query
block:("contains this string")
```

or possibly even Dataview / Datacore output, which would be more powerful and flexible, but would need to return the right type (obviously can't return non-continuous lines nor modified lines etc, must just be a direct transclusion).

Maybe the syntax could be like to prefix the transclusion with query: or other specifier, and but the query expression inside the transclusion operator, like this

```sync
query: ![[ block:("contains this string") ]]
```

Why would this be cool? Because it allows ways to easily grab entire lists (and sublists) of content, in addition to heading-delimited sections. For people like myself who enjoy the outliner approach to notes, this gives a great way to replace the built-in Linked Mentions entirely. Imagine in the following image if the query content on the right were directly editable -- bliss!

By the way, I want you to know how incredible this work already is -- editable transclusions is truly something that fits right in with the way I think most of us want Obsidian to feel like. You've done a great job, and we appreciate it very much!

[uthvah]

@parkeraddison, thank you so much for the kind words!

This is an incredible idea, but it’s also a massive architectural challenge. Syncing non-contiguous search results back to multiple source files requires a very robust 'source-mapping' logic to prevent data corruption.

I've converting this to a Discussion so we can brainstorm the implementation. I'm specifically curious about your thoughts on:

• Starting with Block ID support (![[^blockid]]) as a middle-ground for outliners.
• How we should handle the UI if a query returns results from 10 different files at once.

Similar idea: https://www.reddit.com/r/ObsidianMD/comments/1njvm7x/comment/neuss0m/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

[uthvah]

Maybe this kind of system would be ideal?

• Query Engine: Use Dataview/Obsidian API to find targets.
• Display Engine: Render targets as lightweight, static HTML (Opening 5+ WorkspaceLeaves would cause performance issues)
• Edit Engine: On interaction, seamlessly hot-swap the static HTML with the existing WorkspaceLeaf logic, restricted to a specific Block ID (rather than the existing line based logic). Destroy it when the user clicks off.