Feature Request: Obsidian Dataview integration

[gmarchand]

Is your feature request related to a problem? Please describe.

When working with Obsidian vaults that heavily rely on Dataview queries (inline queries, dataview code blocks, dataviewjs blocks), Mark Sharp currently does not render or interpret them — they appear as raw code blocks. This makes it frustrating to use Mark Sharp as a companion editor for Dataview-powered vaults, since key content remains invisible or unformatted.

Describe the solution you'd like

Add support for rendering Dataview query blocks within Mark Sharp, including:

• dataview code blocks: execute and render the results of DQL (Dataview Query Language) queries as tables, lists, or task views.
• dataviewjs code blocks: support for JavaScript-based Dataview queries.
• Inline Dataview expressions: render `= expression` inline queries within text.

Ideally, this would work by either:

1. Integrating with the Dataview plugin API when running inside Obsidian, or
2. Providing a standalone rendering layer that parses and evaluates DQL queries against the local vault metadata (frontmatter, tags, file paths, etc.).

Describe alternatives you've considered

• Falling back to displaying Dataview blocks as styled read-only code blocks (non-evaluated), which would at least avoid rendering them as plain unstyled text.
• Delegating rendering to the Obsidian plugin API directly via a bridge/hook, rather than reimplementing Dataview logic from scratch.
• Using the Dataview API exposed by the plugin to query results at render time.

Additional context

Dataview is one of the most widely used Obsidian community plugins (4M+ downloads), and many vaults depend on it for structured data views, dashboards, and task management. Supporting it in Mark Sharp would significantly improve compatibility with real-world Obsidian vaults.

Reference: obsidian-dataview on GitHub