It might still be desired to use markdown formatting in alternative text after pipe character in wikilink.
I use markdown-style links and I think, markdown formatting should be ignored in url part of the link. Unfortunately many existing parsers do not respect this. It is headache when I have to reference some stupid folder/file names as reported and still completely unresolved in:
- How to both store and render raw path in functional link
- Code enclosed in backticks does not preserve double/consecutive spaces
Related: Support underscores "_" in block-id
Proposed solution:
Develop syntax to reference links from YAML header where they can be easily stored as “block literals” which conveniently do not require encoding in YAML. markdown
Reference-style link syntax could be used for this. If markdown reference definition is not found, then check if anchor exists in YAML front-matter.
---
related:
- &YAMLAnchor1 file1.md
- &Anchor2 file2.md
- file3.md
---
Possible options to consider:
- [text][YAMLAnchor1] %% reference-style + YAML anchors %%
- [[{{Anchor2}}|text]] or [text]({{Anchor2}}) %% some syntax for referencing variables %%
- ...