fss-link 1.2.22 → 1.2.24

package/bundle/fss-link.js

@@ -22371,7 +22371,7 @@ async function createContentGeneratorConfig(config, authType) {
 async function createContentGenerator(config, gcConfig, sessionId2) {
   if (DEBUG_CONTENT)
     console.log(`\u{1F41B} DEBUG createContentGenerator: authType=${config.authType}, apiKey=${config.apiKey}, baseUrl=${config.baseUrl}`);
-  const version = "1.2.22";
+  const version = "1.2.24";
   const userAgent = `FSS-Link/${version} (${process.platform}; ${process.arch})`;
   const baseHeaders = {
     "User-Agent": userAgent
@@ -69326,7 +69326,7 @@ IMPORTANT: Always use the ${TodoWriteTool.Name} tool to plan and track tasks thr
 
   **Use dedicated tools for:**
   - File reading: '${ReadFileTool.Name}', '${ReadManyFilesTool.Name}' (NOT cat/head/tail)
-    - *Why*: Curated display with line numbers, user-friendly formatting, optional metadata
+    - *Why*: Curated display with line numbers, user-friendly formatting, optional metadata. When editing, extract only the actual code (ignore line number prefixes).
   - File searching: '${GlobTool.Name}' (NOT find/ls)
     - *Why*: Enhanced results with icons, grouping, git-ignore awareness
   - Content searching: '${GrepTool.Name}' (NOT bash grep/rg)
@@ -69520,7 +69520,7 @@ tests/test_auth.py
 </tool_call>
 <tool_call>
 <function=read_file>
-<parameter=path>
+<parameter=absolute_path>
 /path/to/tests/test_auth.py
 </parameter>
 <parameter=offset>
@@ -69536,7 +69536,7 @@ Great, 'tests/test_auth.py' exists and covers the core authentication logic. Wit
 I'll also confirm 'requests' is a dependency.
 <tool_call>
 <function=read_file>
-<parameter=path>
+<parameter=absolute_path>
 /path/to/requirements.txt
 </parameter>
 </function>
@@ -69552,13 +69552,13 @@ Here's the plan:
 
 <tool_call>
 <function=replace>
-<parameter=path>
-src/auth.py
+<parameter=file_path>
+/path/to/src/auth.py
 </parameter>
-<parameter=old_content>
+<parameter=old_string>
 (old code content)
 </parameter>
-<parameter=new_content>
+<parameter name="new_string">
 (new code content)
 </parameter>
 </function>
@@ -69587,7 +69587,7 @@ model:
 Okay, I can write those tests. First, I'll read someFile.ts to understand its functionality.
 <tool_call>
 <function=read_file>
-<parameter=path>
+<parameter=absolute_path>
 /path/to/someFile.ts
 </parameter>
 </function>
@@ -69599,9 +69599,12 @@ Now I'll look for existing or related test files to understand current testing c
 (After reviewing existing tests and the file content)
 <tool_call>
 <function=write_file>
-<parameter=path>
+<parameter=file_path>
 /path/to/someFile.test.ts
 </parameter>
+<parameter=content>
+(test content here)
+</parameter>
 </function>
 </tool_call>
 I've written the tests. Now I'll run the project's test command to verify them.
@@ -95583,7 +95586,7 @@ async function getPackageJson() {
 // packages/cli/src/utils/version.ts
 async function getCliVersion() {
   const pkgJson = await getPackageJson();
-  return "1.2.22";
+  return "1.2.24";
 }
 
 // packages/cli/src/ui/commands/aboutCommand.ts
@@ -95635,7 +95638,7 @@ import open4 from "open";
 import process11 from "node:process";
 
 // packages/cli/src/generated/git-commit.ts
-var GIT_COMMIT_INFO = "01c4caed";
+var GIT_COMMIT_INFO = "ceabf39e";
 
 // packages/cli/src/ui/commands/bugCommand.ts
 init_dist2();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "fss-link",
-  "version": "1.2.22",
+  "version": "1.2.24",
   "engines": {
     "node": ">=20.0.0"
   },