Skip to content

docs: fix broken Flashblocks FAQ anchor links - #1844

Open
devorun wants to merge 1 commit into
base:masterfrom
devorun:fix/flashblocks-faq-anchor-links
Open

docs: fix broken Flashblocks FAQ anchor links#1844
devorun wants to merge 1 commit into
base:masterfrom
devorun:fix/flashblocks-faq-anchor-links

Conversation

@devorun

@devorun devorun commented Aug 21, 2026

Copy link
Copy Markdown

What changed? Why?

Two pages link into the Flashblocks FAQ using fragments derived from <Accordion> titles:

  • eth_callflashblocks/faq#why-does-eth_call-pending-report-a-block-number-several-blocks-behind-tip
  • Flashblocks API overview → flashblocks/faq#can-the-flashblock-index-exceed-10-is-that-a-bug

Accordion titles are not headings, so no anchor is generated for them and neither fragment resolves. Both links currently land at the top of the FAQ instead of the relevant answer.

This repoints them to the headings of the sections that contain those accordions:

  • the eth_call "pending" answer lives under ## RPC#rpc
  • the Flashblock index answer lives under ## WebSocket#websocket

Notes to reviewers

These are the only two cross-references in the docs that target accordion titles rather than headings; every other anchor link points at a real heading. Section-level anchors are the closest working targets without adding explicit anchors to the FAQ. Only the two linking pages are touched — faq.mdx itself is unchanged.

How has it been tested?

Checked that flashblocks/faq.mdx contains no headings matching either fragment, and confirmed the two answers sit under the ## RPC and ## WebSocket headings whose anchors are #rpc and #websocket.

@cb-heimdall

Copy link
Copy Markdown
Collaborator

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/2
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 1
Sum 2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants