feat: Obsidian-style [[wikilinks]] in content
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start with Fanstatic/Helpers/SiteHelper.cs to see how Markdig extensions are registered, then read Parsers/RefShortcodeParser.cs for reference resolution and its error handling. Inspect the test conventions in Fanstatic.Test/ and fixture sites in .TestSites/; run ./build.sh test. Done means the acceptance cases resolve to expected permalinks, unresolved links log errors, and MissingWikiLinkAsError: true fails the build.
由索引模型根据 Issue 内容生成。
描述
Current State
Markdown content cannot express Obsidian-style [[wikilinks]]. Markdig's UseAdvancedExtensions() (Fanstatic/Helpers/SiteHelper.cs:18-20)
has no wikilink extension, so [[target]] renders as literal text. Hugo sites resolve [text](_)
links through a _markup/render-link.html hook; that is tracked separately by #34.
Tasks:
- New Markdig inline extension recognizing
[[target]]and[[target|label]](Helpers/WikiLinkExtension.cs) - Resolve
targetmirroringref/relref(Parsers/RefShortcodeParser.cs): a content path such as
posts/foo.mdor/posts/foo.md, and a taxonomy target such astags/sucos; a bare[[sucos]]
tries a taxonomy term first, then a page by path/name. Language and output format default to the
calling page's. - Unresolved target renders a link to
./and logs an error (build keeps going), matchingRefShortcodeParser -
fanstatic.yamlsettingMissingWikiLinkAsError(bool, defaultfalse) to escalate unresolved
wikilinks to build-failing errors - Alias resolution is intentionally out of scope (aliases are a post-processed page element)
Tests live in Fanstatic.Test/ (xUnit + NSubstitute); fixture sites in .TestSites/. Run ./build.sh test; new/changed methods need CRAP ≤ 15 and ≥ 75 % line coverage.
Acceptance Criteria:
- Fixture site:
[[posts/foo.md]],[[tags/x]], and bare[[x]]resolve to the expected permalinks;
[[unknown]]renders./with an error logged; withMissingWikiLinkAsError: truethe build fails.
Related:
- #33 (Phase 3 epic, parent)
- #34 (render hooks for links and images; wikilink output can later route through it)
- #40 (Markdown extensions configurable in YAML)
- 主要语言
- C#
- 星标
- 1
- 派生
- 0
- 平均合并
- 7 小时
- 30 天内合并 PR
- 6
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
MASS4ORG/Fanstatic 的其他 Issue
-
c:templates p:low size:S t:task
难度 5/5 一周以上 新手友好度 45/100
维护者通常 1 天内回复
-
c:content good first issue p:low size:S t:feature
难度 4/5 3-5 天 新手友好度 58/100
维护者通常 1 天内回复
-
c:templates p:medium size:M t:feature
难度 5/5 一周以上 新手友好度 35/100
维护者通常 1 天内回复
-
c:content p:medium size:L t:feature
难度 5/5 一周以上 新手友好度 35/100
维护者通常 1 天内回复
-
c:templates p:medium size:S t:feature
难度 4/5 3-5 天 新手友好度 57/100
维护者通常 1 天内回复
查看 MASS4ORG/Fanstatic 的全部 Issue
相似的 Issue
-
alerts bug effort:S P2
难度 2/5 1-3 小时 新手友好度 76/100
nightscout/nocturne#2511 ·
维护者通常 1 天内回复
-
feature-request
难度 2/5 1-3 小时 新手友好度 77/100
stripe/stripe-dotnet#3484 ·
维护者通常 2 天内回复
-
bug mcp misleading small
难度 2/5 1-3 小时 新手友好度 77/100
维护者通常 1 天内回复
-
accessibility help wanted macos
难度 2/5 1-3 小时 新手友好度 70/100
dorlugasigal/annotator#42 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 75/100
AvaloniaUI/Avalonia#22568 ·
维护者通常 2 天内回复