[Bug]: [Policy Hub] In-page anchor links in policy docs go to the Policy Hub home page instead of the section
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 75/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- html, typescript
- 领域
- frontend
调研方向
Start with frontend/index.html, MarkdownRenderer.tsx, and TableOfContents.tsx, which the issue identifies as the sources of the two failures. Trace how fragment links are resolved with the base URL and when policy headings receive IDs after docs load. Reproduce using the llm-cost policy link, then verify both clicking an in-page link and opening a policy URL with a fragment land on the section.
由索引模型根据 Issue 内容生成。
描述
Please select the area the issue is related to
Gateway
Please select the aspect the issue is related to
Aspect/API (API backends, definitions, contracts, interfaces, OpenAPI), Aspect/UX (User experience, flows, usability, clarity)
Description
In-page anchor links in policy docs, such as [Adding Your Own Pricing](#adding-your-own-pricing), don't work on the Policy Hub. Clicking one loads the hub's home page instead of jumping to the section. The links are standard markdown and work on GitHub.
There are two causes, both in the frontend:
<base>redirects fragment links.frontend/index.html(lines 11–25) injects<base href="/api-management/policy-hub/">. With a<base>element, the browser resolves every relative URL against the base URL, fragment-only links included. So#adding-your-own-pricingbecomes/api-management/policy-hub/#adding-your-own-pricing, which is the hub root.MarkdownRenderer.tsxpasses these links through unchanged, because itsurlTransform(line 193) only rewrites URLs that start with..- Sections can't be linked to directly. Opening
/policies/<name>#<section>leaves the page at the top. Docs are fetched after the page has loaded, and headings only getids afterwards, whenTableOfContents.tsxtags them (lines 54–59,h2/h3only). When the browser tries to jump to the fragment, the heading doesn't exist yet.
Impact:
21 of the 72 policies on the hub have these links in their latest published version, 71 links in total:
mtls-auth (14), typesafe-jev-mcp-tool-intent-verification (7), opa-policy (6), typesafe-jev-mcp-tool-result-screening (6), typesafe-jev-tool-filtering (5), aws-authentication (4), jwt-auth (4), semantic-cache (4), typesafe-jev-content-safety (4), oauth2-generator (3), backend-jwt (2), mcp-authz (2), mcp-tool-schema-validator (2), error-response-formatter (1), llm-cost (1), llm-cost-based-ratelimit (1), log-message (1), mcp-auth (1), oauth2-token-exchange (1), opaque-token-auth (1), typesafe-jev-model-routing (1).
16 of these 21 also have older versions with the same links.
Steps to Reproduce
- Open https://choreolabs.com/api-management/policy-hub/policies/llm-cost.
- In the Notes section, click Adding Your Own Pricing.
- Expected: the page scrolls to the "Adding Your Own Pricing" section.
Actual: the browser loads https://choreolabs.com/api-management/policy-hub/#adding-your-own-pricing, the hub's home page. - Open https://choreolabs.com/api-management/policy-hub/policies/llm-cost#adding-your-own-pricing directly.
Expected: the page opens at that section.
Actual: the page stays at the top.
The same happens with any in-page link on the policies above, for example the 14 links on https://choreolabs.com/api-management/policy-hub/policies/mtls-auth.
Severity Level of the Issue
Severity/Minor (Non-critical functionality. Can be fixed in future releases)
Environment Details (with versions)
- Seen in production at https://choreolabs.com/api-management/policy-hub/
- Reproduced locally with the frontend dev server (
npx vite) against the public production API fromfrontend/public/config.js, in Chrome on macOS.
- 主要语言
- Go
- 星标
- 85
- 派生
- 137
- 平均合并
- 1 天 12 小时
- 30 天内合并 PR
- 247
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
wso2/api-platform 的其他 Issue
-
Area/DeveloperPortal Aspect/UI Severity/Minor Type/Bug
难度 1/5 1 小时以内 新手友好度 88/100
wso2/api-platform#4369 ·
维护者通常 1 天内回复
-
[Bug]: host-rewrite policy documentation lists fewer allowed host characters than the policy accepts未关闭Area/Policies Aspect/Other Severity/Trivial Type/Bug
难度 1/5 1 小时以内 新手友好度 91/100
wso2/api-platform#4355 ·
维护者通常 1 天内回复
-
Area/Gateway Aspect/API Severity/Minor Type/Bug
难度 2/5 1-3 小时 新手友好度 78/100
wso2/api-platform#4348 ·
维护者通常 1 天内回复
-
Aspect/AI Aspect/API. Severity/Major
难度 2/5 1-3 小时 新手友好度 77/100
wso2/api-platform#4343 ·
维护者通常 1 天内回复
-
Area/Policies Aspect/Configuration Severity/Minor Type/Bug
难度 2/5 1-3 小时 新手友好度 74/100
wso2/api-platform#4330 ·
维护者通常 1 天内回复
查看 wso2/api-platform 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 82/100
-
needs discussion
难度 2/5 1-3 小时 新手友好度 78/100
openfga/openfga.dev#1436 · 1 条评论 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
digital-go-jp/abr-geocoder#457 ·
维护者通常 3 天内回复
-
benchmark
难度 1/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 77/100
mozilla-ai/cq#601 ·
维护者通常 1 天内回复