Live preview shows inline metadata as links
See original GitHub issueWhat happened?
In live preview, type:
[prop1:val1] [prop2:val2]
(one space separation between properties)
You get:
DQL
No response
JS
No response
Dataview Version
0.4.26
Obsidian Version
0.14.6
OS
MacOS
Issue Analytics
- State:
- Created a year ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Best Practices for Link Previews in Messages
When people send messages containing links to web sites, Messages in iOS and macOS will automatically generate inline previews for the links.
Read more >Use Link Preview in Outlook.com and Outlook on the web
When you add a URL to an email, using Link preview, you get a rich preview of a title, thumbnail, and a description...
Read more >Inline Query for Live Preview · Issue #729
I wonder if you could implement Inline Queries for Live Preview as you have for normal dataview queries. Why it is useful. learning...
Read more >The Trick to Disabling Link Previews for URLs in Your ...
When a link is sent via an SMS or iMessage conversation in Messages, the app will automatically change the URL into an inline...
Read more >Core Syntax - MyST-Parser - Read the Docs
Inline Code. `code`. Autolink. <https://www.example.com>. URL Link ... HTML metadata can also be added globally in the conf.py via the myst_html_meta ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I don’t think this will work since
[...] [...]
is valid (or almost valid, not sure about the space in-between) syntax: Commonmark example 526What about
[field1:: key1, field2:: key2]
?I’m open to ergonomic alternative syntaxes; I’m not sure if I can override this specific Obsidian behavior. I’ve just separated my fields via bars,
which fixes rendering issues.