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

[Bug]: A Markdown document opened through /file/ shows its title twice, under links meant for framework component docs

Abierto Apto para principiantes
  • ¿Algo no está bien?
#90 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
78/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
html, markdown, python
Área
frontend

Línea de trabajo

Lee la ruta /file/<path:filepath> en web/blueprints/docs.py y la lógica de renderizado en web/templates/docs_detail.html. Comprueba cómo determina la ruta el título y cómo la plantilla renderiza html_content y sus enlaces. Se considera terminado cuando el título de un documento Markdown aparece una sola vez y no se muestran enlaces exclusivos de componentes para documentos sin una tarjeta de componente.

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

Descripción

area:watchtower bug severity:low status:released triaged
Bug Description

Any project document opened in Watchtower through /file/<path>.md shows its title twice, with two links between the copies that do not apply to it.

Cause, read in the code (1.8.6):

  • web/blueprints/docs.py, route /file/<path:filepath>, lines 245 to 252: the page title is taken from the first line of the file that starts with #.
  • web/templates/docs_detail.html: line 2 prints <h1>{{ page_title }}</h1>, lines 4 and 6 print "Back to Component Docs" and "View in Fabric", and line 11 prints {{ html_content | safe }}, the whole document rendered from Markdown, first heading included.

So every Markdown file that starts with a level-1 heading, the normal shape of a document, shows that heading twice. The "View in Fabric" link goes to /fabric/component/<file stem>, which answers "Not Found" for a document that has no component card.

Steps to Reproduce
  1. Put a Markdown file that starts with # Some title under docs/reports/ in a consumer project.
  2. Open /file/docs/reports/<file>.md in Watchtower.
  3. Click "View in Fabric".
Expected Behavior

The title appears once. The two links appear only for a file that has a Fabric component card; a project document links back to the task that references it, or to nothing.

Actual Behavior
← Back to Component Docs | View in Fabric

The served page contains two <h1> elements with the same text. "View in Fabric" opens a page titled "Not Found".

fw doctor output
AI Agent

Claude Code

Operating System

Linux

Additional Context

Version: 1.8.6 (1ea10441f), vendored consumer. First seen on 1.8.3; the two files are byte-identical between the versions. Checked again on a served page of 1.8.6.

It cannot be fixed on the project side: removing the level-1 heading makes the route pick the first ## heading as page title, and leaves the document without a title once exported; a local patch of the template is overwritten by fw upgrade.

Suggestions:

  1. When the title comes from the document's first heading, drop that heading from html_content before rendering, or do not print page_title in the page header.
  2. Show "Back to Component Docs" and "View in Fabric" only when the file has a Fabric component card.
Lenguaje dominante
Shell
Estrellas
16
Forks
6
Merge medio
6 h 24 min
PR fusionados (30 d)
5

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 DimitriGeelen/agentic-engineering-framework

Todos los issues de DimitriGeelen/agentic-engineering-framework

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.