Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta Adatta ai principianti
  • Qualcosa non va?
#90 4 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
78/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
html, markdown, python
Ambito
frontend

Direzione di ricerca

Leggi la route /file/<path:filepath> in web/blueprints/docs.py e la logica di rendering in web/templates/docs_detail.html. Controlla come la route determina il titolo e come il template visualizza html_content e i suoi link. Il lavoro è completato quando il titolo di un documento Markdown appare una sola volta e i link esclusivi dei componenti non vengono mostrati per i documenti senza una scheda del componente.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.
Lingua principale
Shell
Stelle
16
Fork
6
Merge medio
6h 24m
PR unite (30g)
5

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di DimitriGeelen/agentic-engineering-framework

Tutte le issue di DimitriGeelen/agentic-engineering-framework

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.