Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

feat: Obsidian-style [[wikilinks]] in content

Cerrado
  • ¿Algo no está bien?
#51 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
csharp
Área
backend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

c:content p:medium size:M t:feature
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 target mirroring ref/relref (Parsers/RefShortcodeParser.cs): a content path such as
    posts/foo.md or /posts/foo.md, and a taxonomy target such as tags/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), matching RefShortcodeParser
  • fanstatic.yaml setting MissingWikiLinkAsError (bool, default false) 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; with MissingWikiLinkAsError: true the 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)
Lenguaje dominante
C#
Estrellas
1
Forks
0
Merge medio
7 h
PR fusionados (30 d)
6

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de MASS4ORG/Fanstatic

Todos los issues de MASS4ORG/Fanstatic

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.