mProjectsCode / mProjectsCode/obsidian-meta-bind-plugin
Allow to export as standard markdown (in API)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1k
- Forks
- 86
- PR merge metrics
- No merged PRs in 30d
Description
Is your Feature Request Related to a Problem?
I'm the main maintener of Obsidian Publisher a plugin that "export"/"send" file from Obsidian to a repository. It converts different syntax, from Obsidian to Dataview, in standard markdown with a lot of option.
I use mainly Publisher for my roleplay, and I restraint to use Meta-bind for this (and struggle with Dataview and theses multiple bug) because the lack of possibility to convert meta-bind syntaxes to their content.
Describe the Feature you'd Like
A function in API that convert the syntax to their content. For example,
---
someInputValue: 1
someComputedValue: 2
---
Input: `INPUT[number:someComputedValue]`
Computed Value: `VIEW[{someInputValue} * 2][math:someComputedValue]`
To this:
---
someInputValue: 1
someComputedValue: 2
---
Input: `2`
Computed Value: `2`
Additional Context
Similarly, from what we found using Dataview:
- My code to convert dataview
dvApi.tryQueryMarkdown()dvApi.evaluateInline(query, path);
…
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Dataview conversion code and the referenced dvApi.tryQueryMarkdown() and dvApi.evaluateInline(query, path) methods. Determine which Meta Bind syntax should be supported and expose an API conversion result that matches the example, including evaluated input and computed values. Done means the documented example converts to standard Markdown content.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100