Repository navigation
fix(access): place raw API toggle beside title - #399
Conversation
caigee-cmd
left a comment
There was a problem hiding this comment.
UI change itself is fine: the Show raw API control belongs next to the Native API title, collapsed secondary / expanded ghost is the right contrast, and the bilingual fragment matches.
Do not merge from this head. It conflicts with main after #400 — the only real source change is a few lines in RawApiPanel.tsx, the rest is a stale hashed internal/webui/static pair.
Please rebase onto current main, run cd frontend && npm run sync, and push, or close this and open a clean PR with just the panel + changelog + freshly synced static assets.
caigee-cmd
left a comment
There was a problem hiding this comment.
Architecture: this is console UI only (frontend + synced internal/webui/static). No gateway/executor/runtime/store movement, HeroUI-only, bilingual fragment present. The remaining rule is the embed contract: do not merge a stale hashed JS/CSS pair. Rebase main and cd frontend && npm run sync before landing.
c1d75a6 to
1521a83
Compare
Rebased onto main after #403; regenerated webui static assets.
1521a83 to
96e5e98
Compare
Summary
/access「展开原始 API」 / Show raw API control next to the Native API title (left-aligned), instead ofjustify-betweenon the far right.secondary(project has noprimarybutton variant in use); when expanded, quieterghost.internal/webui/staticfor CI; add bilingual changelog fragment.Notes
RawApiPanel; no parallel Access pages, no deploy/release.Test plan
/access, confirm the Show raw API control sits beside the Native API heading (not far right).