docs: describe DirectoryReadResultSchema as the shape both eras share (#2374 review)
Its doc comment still called it the legacy result, though both eras now parse with it once the codec has removed resultType. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Q3RsrgCxVoFPokLB4vAkxi Signed-off-by: cliffhall <cliff@futurescale.com>
This commit is contained in:
parent
e53f6a1bf0
commit
f3e0edd257
1 changed files with 4 additions and 2 deletions
|
|
@ -235,8 +235,10 @@ export type GetSkillResult = SkillEntry;
|
|||
export const DirectoryChildSchema = ResourceSchema;
|
||||
|
||||
/**
|
||||
* `resources/directory/read` result on a **legacy** connection: the directory's
|
||||
* direct children plus the opaque cursor.
|
||||
* `resources/directory/read` result on **either** era: the directory's direct
|
||||
* children plus the opaque cursor. On a modern connection this is the shape
|
||||
* after the SDK codec has checked and removed `resultType`, which is why no
|
||||
* modern variant exists — see the note below (#2373).
|
||||
*
|
||||
* `looseObject`, matching every other result schema here: a server that also
|
||||
* sends the caching attributes is not wrong for doing so, and a schema is not
|
||||
|
|
|
|||
Loading…
Reference in a new issue