refactor: renamed intent field from _i to i
- Renamed the global `INTENT_FIELD` constant from `_i` to `i`. - Updated documentation strings, type annotations, and test expectations across packages to reflect the new field name. - Ensured consistent usage of the constant in tool schema construction and intent serialization.
This commit is contained in:
@@ -170,7 +170,7 @@ describe("formatSessionDumpText markdown-headings transcript", () => {
|
||||
expect(out).toContain("### Tool Result: read");
|
||||
expect(out).toContain("### Tool Call: read");
|
||||
expect(out).toContain("path: src/foo.ts");
|
||||
// The `_i` intent renders as a `//` comment under the heading, never inside the YAML args.
|
||||
// The `i` intent renders as a `//` comment under the heading, never inside the YAML args.
|
||||
expect(out).toContain("// Reading the file");
|
||||
expect(out).not.toContain(`${INTENT_FIELD}:`);
|
||||
// Tool calls render as a readable heading + YAML, never the <invoke>/<parameter> XML.
|
||||
|
||||
Reference in New Issue
Block a user