Anchors in markdown spec no longer work in GitHub navigation #1144

Activity

1. char0n

   added

   🐞 Bug

   on Dec 11, 2025
2. char0n

   added the

   Bug

   issue type on Dec 11, 2025
3. char0n

   added this to Spec Triageon Dec 11, 2025
4. github-project-automation

   moved this to Todo in Spec Triageon Dec 11, 2025
5. Harsh-Sahu43 commented on Dec 12, 2025

   

   Harsh-Sahu43

   on Dec 12, 2025

   More actions

   Hi, I’m Harsh Sahu. I would like to work on this issue.
   To confirm: the task is to convert all heading anchors and all their internal references from camelCase to kebab-case across the spec markdown file.
   Please let me know if I can proceed with a PR.
6. char0n commented on Dec 12, 2025

   

   char0n

   on Dec 12, 2025

   MemberAuthor

   More actions

   Hi @Harsh-Sahu43,

   the task is to convert all heading anchors and all their internal references from camelCase to kebab-case across the spec markdown file.

   Exactly
7. char0n

   assigned

   Harsh-Sahu43

   on Dec 12, 2025
8. Harsh-Sahu43 commented on Dec 13, 2025

   

   Harsh-Sahu43

   on Dec 13, 2025

   More actions

   Thanks for the confirmation and for assigning this issue.

   I’ll proceed with updating all heading anchors and their internal references from camelCase to kebab-case across the spec markdown file and will open a PR shortly.
9. Harsh-Sahu43 commented on Dec 13, 2025

   

   Harsh-Sahu43

   on Dec 13, 2025

   More actions

   Hi @char0n,

   Just to confirm scope before proceeding:
   should this change cover all internal anchors used for navigation, including

   1. markdown-generated heading anchors (e.g. ## serversObject), and
   2. explicit HTML anchors (e.g. <a name="definitionsServer"></a>),
      along with updating all internal references to match kebab-case?

   I’ll proceed accordingly once confirmed.
   Thanks!
10. char0n commented on Dec 13, 2025

    

    char0n

    on Dec 13, 2025

    MemberAuthor

    More actions

    should this change cover all internal anchors used for navigation, including

    Yes, that's right. Confirmed

    👍React with 👍1Reacted by Harsh Sahu
11. github-project-automation

    moved this from Todo to In Progress in Spec Triageon Dec 14, 2025
12. github-actions commented on Apr 13, 2026

    

    github-actionsbot

    on Apr 13, 2026 – with GitHub Actions

    More actions

    This issue has been automatically marked as stale because it has not had recent activity 😴

    It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

    There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

    Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

    Thank you for your patience ❤️
13. github-actions

    added

    stale

    on Apr 13, 2026