pauljd/vectorcraft
1
0
Fork 0
mirror of https://github.com/storytold/vectorcraft.git synced 2026-11-13 09:39:52 +00:00
Code Issues Packages Projects Releases Wiki Activity

MCP: a readable library's id keeps a hidden path that it holds after its start

Browse Source 
A reply hid a hidden library's absolute path wherever it appeared, also
inside another loaded library's id when the match began after the id's
start. With `/libs/Kit.gpl` hidden, the readable id
`loaded//project/libs/Kit.gpl` came back as `loaded//projectKit.gpl`,
and a request that used it failed.

Each whole readable id in a reply (with or without `loaded/`, or in a
`file:` URL with no host or `localhost`) is now found first, and a
hidden id or path that lies inside it stays. The same path after a
drive or in a URL with another host is still hidden.
This commit is contained in:
dotCooCoo
2026-11-12 12:29:20 -08:00
parent 41f384bffc
commit cbfe5248bb
3 changed files with 74 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/mcp.md
+2 -2
View File
@@ -178,8 +178,8 @@ the suite) keep the agent to the folders you give it:
(`ui.palette_query`), a script's report (`scriptReport`), a screenshot's reply and the error from an internal
fault included, for the libraries hidden before the request ran and after it. The path is also matched with `%XX` escapes as a `file:`
URL writes it, and on Windows in any case of its letters; a `file:` URL of an absolute path is shown as the file
name alone, without `file:` or its host. A hidden id or path stays only where it begins
another loaded library's whole id with no `.` or `..` part, so a readable library's id that begins with a hidden one stays. A reply also shows a path outside the
name alone, without `file:` or its host. A hidden id or path stays only where it lies inside
another loaded library's whole id with no `.` or `..` part, so a readable library's id that begins with or holds a hidden one stays. A reply also shows a path outside the
read roots that the request sent by its file name, whether or not a library was loaded from it and whether the
request succeeded or failed, so that the reply reads the same either way. The one exception is the `path`
and `files` entries of a reply's result, a `command.batch` step's result included, that name the file the