Nested Frontmatter
pendingby Tony Xiao
Render nested frontmatter objects and arrays inside the native Properties pane.
Nested Frontmatter
Render nested frontmatter arrays and objects inside the native Properties pane.
What it does
Scalar frontmatter values already read well, but nested objects and arrays often collapse into hard-to-read JSON-like blobs inside Properties. Nested Frontmatter makes those values readable by rendering them as structured rows while keeping the native Properties UI.
Current scope:
- Enhances nested object/array values that Obsidian renders as
unknownproperties - Preserves Obsidian's existing property row layout and styling as much as possible
- Makes nested wikilinks navigable with a single click
What it does not do
- It does not create a new metadata editor
- It does not change your frontmatter data format
- It does not add vault-specific schemas or assumptions
Development
There is no bundling step. main.js is the source file Obsidian loads.
pnpm install
pnpm check
pnpm test
GitHub Actions
CIruns typechecking and tests on every push and pull request.Releaseruns the same verification, packagesmain.js,manifest.json, andversions.json, and publishes a GitHub release when you push av*tag such asv0.1.0.
Testing
The test suite covers:
- structured frontmatter parsing
- wikilink parsing
- DOM enhancement of unknown property rows
- single-click nested link navigation behavior
- regression protection against unnecessary rerender loops
Status
This plugin is intentionally narrow. The goal is to make nested frontmatter readable in the native Properties pane and do that one thing well.
For plugin developers
Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.