docs: shape.md — fix stale app.js example, app.js no longer exists
argus, non-blocking note on PR#3702: the relative-path-resolution example still used static/app.js as its illustrative filename after that file was deleted in the cutover. Mechanism described was still correct, just a stale filename a future reader could get confused chasing. Swapped to static/main.js (the agent page's own script) and static/stats.js (the /stats subpage example, more accurate than main.js there since that's specifically about a subpage's own script).
This commit is contained in:
parent
fa2b360e74
commit
8e97fc6263
1 changed files with 4 additions and 4 deletions
|
|
@ -308,7 +308,7 @@ two modes coexist while sub-agents transition.
|
|||
|
||||
The per-agent UI uses **document-relative paths everywhere** for
|
||||
assets, API calls, form actions, and the screen WebSocket. Bare
|
||||
references like `static/app.js`, `api/state`, `events/stream`,
|
||||
references like `static/main.js`, `api/state`, `events/stream`,
|
||||
`screen/ws` resolve against `document.baseURI` — the page's URL
|
||||
without its last path segment.
|
||||
|
||||
|
|
@ -328,8 +328,8 @@ paths server-side. Only the browser-facing URLs are gated on the
|
|||
mount prefix.
|
||||
|
||||
Subpages (`stats`, `screen`) are served without a trailing slash so
|
||||
the relative-path resolution stays correct: `static/app.js` from
|
||||
`/stats` becomes `/static/app.js` (last segment `stats` gets
|
||||
replaced), not `/stats/static/app.js`. Adding a trailing slash to
|
||||
the relative-path resolution stays correct: `static/stats.js` from
|
||||
`/stats` becomes `/static/stats.js` (last segment `stats` gets
|
||||
replaced), not `/stats/static/stats.js`. Adding a trailing slash to
|
||||
those routes would break the resolution; either keep them
|
||||
slash-less or use `<base href>` injection at serve time.
|
||||
|
|
|
|||
Loading…
Reference in a new issue