fss-link 1.0.49 → 1.0.51

package/dist/ui/commands/initCommand.test.ts

@@ -1,127 +0,0 @@
-/**
- * @license
- * Copyright 2025 Google LLC
- * SPDX-License-Identifier: Apache-2.0
- */
-
-import { vi, describe, it, expect, beforeEach, afterEach } from 'vitest';
-import * as fs from 'fs';
-import * as path from 'path';
-import { initCommand } from './initCommand.js';
-import { createMockCommandContext } from '../../test-utils/mockCommandContext.js';
-import { type CommandContext } from './types.js';
-
-// Mock the 'fs' module with both named and default exports to avoid breaking default import sites
-vi.mock('fs', async (importOriginal) => {
-  const actual = await importOriginal<typeof import('fs')>();
-  const existsSync = vi.fn();
-  const writeFileSync = vi.fn();
-  const readFileSync = vi.fn();
-  return {
-    ...actual,
-    existsSync,
-    writeFileSync,
-    readFileSync,
-    default: {
-      ...(actual as unknown as Record<string, unknown>),
-      existsSync,
-      writeFileSync,
-      readFileSync,
-    },
-  } as unknown as typeof import('fs');
-});
-
-describe('initCommand', () => {
-  let mockContext: CommandContext;
-  const targetDir = '/test/dir';
-  const DEFAULT_CONTEXT_FILENAME = 'LINK.md';
-  const geminiMdPath = path.join(targetDir, DEFAULT_CONTEXT_FILENAME);
-
-  beforeEach(() => {
-    // Create a fresh mock context for each test
-    mockContext = createMockCommandContext({
-      services: {
-        config: {
-          getTargetDir: () => targetDir,
-        },
-      },
-    });
-  });
-
-  afterEach(() => {
-    // Clear all mocks after each test
-    vi.clearAllMocks();
-  });
-
-  it(`should inform the user if ${DEFAULT_CONTEXT_FILENAME} already exists and is non-empty`, async () => {
-    // Arrange: Simulate that the file exists
-    vi.mocked(fs.existsSync).mockReturnValue(true);
-    vi.spyOn(fs, 'readFileSync').mockReturnValue('# Existing content');
-
-    // Act: Run the command's action
-    const result = await initCommand.action!(mockContext, '');
-
-    // Assert: Check for the correct informational message
-    expect(result).toEqual({
-      type: 'message',
-      messageType: 'info',
-      content: `A ${DEFAULT_CONTEXT_FILENAME} file already exists in this directory. No changes were made.`,
-    });
-    // Assert: Ensure no file was written
-    expect(fs.writeFileSync).not.toHaveBeenCalled();
-  });
-
-  it(`should create ${DEFAULT_CONTEXT_FILENAME} and submit a prompt if it does not exist`, async () => {
-    // Arrange: Simulate that the file does not exist
-    vi.mocked(fs.existsSync).mockReturnValue(false);
-
-    // Act: Run the command's action
-    const result = await initCommand.action!(mockContext, '');
-
-    // Assert: Check that writeFileSync was called correctly
-    expect(fs.writeFileSync).toHaveBeenCalledWith(geminiMdPath, '', 'utf8');
-
-    // Assert: Check that an informational message was added to the UI
-    expect(mockContext.ui.addItem).toHaveBeenCalledWith(
-      {
-        type: 'info',
-        text: `Empty ${DEFAULT_CONTEXT_FILENAME} created. Now analyzing the project to populate it.`,
-      },
-      expect.any(Number),
-    );
-
-    // Assert: Check that the correct prompt is submitted
-    expect(result.type).toBe('submit_prompt');
-    expect(result.content).toContain(
-      'You are FSS Link, an interactive CLI agent',
-    );
-  });
-
-  it(`should proceed to initialize when ${DEFAULT_CONTEXT_FILENAME} exists but is empty`, async () => {
-    vi.mocked(fs.existsSync).mockReturnValue(true);
-    vi.spyOn(fs, 'readFileSync').mockReturnValue('   \n  ');
-
-    const result = await initCommand.action!(mockContext, '');
-
-    expect(fs.writeFileSync).toHaveBeenCalledWith(geminiMdPath, '', 'utf8');
-    expect(result.type).toBe('submit_prompt');
-  });
-
-  it('should return an error if config is not available', async () => {
-    // Arrange: Create a context without config
-    const noConfigContext = createMockCommandContext();
-    if (noConfigContext.services) {
-      noConfigContext.services.config = null;
-    }
-
-    // Act: Run the command's action
-    const result = await initCommand.action!(noConfigContext, '');
-
-    // Assert: Check for the correct error message
-    expect(result).toEqual({
-      type: 'message',
-      messageType: 'error',
-      content: 'Configuration not available.',
-    });
-  });
-});

package/dist/ui/commands/initCommand.ts

@@ -1,117 +0,0 @@
-/**
- * @license
- * Copyright 2025 Google LLC
- * SPDX-License-Identifier: Apache-2.0
- */
-
-import * as fs from 'fs';
-import * as path from 'path';
-import {
-  CommandContext,
-  SlashCommand,
-  SlashCommandActionReturn,
-  CommandKind,
-} from './types.js';
-import { getCurrentGeminiMdFilename } from 'fss-link-core';
-
-export const initCommand: SlashCommand = {
-  name: 'init',
-  description: 'Analyzes the project and creates a tailored LINK.md file.',
-  kind: CommandKind.BUILT_IN,
-  action: async (
-    context: CommandContext,
-    _args: string,
-  ): Promise<SlashCommandActionReturn> => {
-    if (!context.services.config) {
-      return {
-        type: 'message',
-        messageType: 'error',
-        content: 'Configuration not available.',
-      };
-    }
-    const targetDir = context.services.config.getTargetDir();
-    const contextFileName = getCurrentGeminiMdFilename();
-    const contextFilePath = path.join(targetDir, contextFileName);
-
-    try {
-      if (fs.existsSync(contextFilePath)) {
-        // If file exists but is empty (or whitespace), continue to initialize; otherwise, bail out
-        try {
-          const existing = fs.readFileSync(contextFilePath, 'utf8');
-          if (existing && existing.trim().length > 0) {
-            return {
-              type: 'message',
-              messageType: 'info',
-              content: `A ${contextFileName} file already exists in this directory. No changes were made.`,
-            };
-          }
-        } catch {
-          // If we fail to read, conservatively proceed to (re)create the file
-        }
-      }
-
-      // Ensure an empty context file exists before prompting the model to populate it
-      try {
-        fs.writeFileSync(contextFilePath, '', 'utf8');
-        context.ui.addItem(
-          {
-            type: 'info',
-            text: `Empty ${contextFileName} created. Now analyzing the project to populate it.`,
-          },
-          Date.now(),
-        );
-      } catch (err) {
-        return {
-          type: 'message',
-          messageType: 'error',
-          content: `Failed to create ${contextFileName}: ${err instanceof Error ? err.message : String(err)}`,
-        };
-      }
-    } catch (error) {
-      return {
-        type: 'message',
-        messageType: 'error',
-        content: `Unexpected error preparing ${contextFileName}: ${error instanceof Error ? error.message : String(error)}`,
-      };
-    }
-
-    return {
-      type: 'submit_prompt',
-      content: `
-You are FSS Link, an interactive CLI agent. Analyze the current directory and generate a comprehensive ${contextFileName} file to be used as instructional context for future interactions.
-
-**Analysis Process:**
-
-1.  **Initial Exploration:**
-    *   Start by listing the files and directories to get a high-level overview of the structure.
-    *   Read the README file (e.g., \`README.md\`, \`README.txt\`) if it exists. This is often the best place to start.
-
-2.  **Iterative Deep Dive (up to 10 files):**
-    *   Based on your initial findings, select a few files that seem most important (e.g., configuration files, main source files, documentation).
-    *   Read them. As you learn more, refine your understanding and decide which files to read next. You don't need to decide all 10 files at once. Let your discoveries guide your exploration.
-
-3.  **Identify Project Type:**
-    *   **Code Project:** Look for clues like \`package.json\`, \`requirements.txt\`, \`pom.xml\`, \`go.mod\`, \`Cargo.toml\`, \`build.gradle\`, or a \`src\` directory. If you find them, this is likely a software project.
-    *   **Non-Code Project:** If you don't find code-related files, this might be a directory for documentation, research papers, notes, or something else.
-
-**${contextFileName} Content Generation:**
-
-**For a Code Project:**
-
-*   **Project Overview:** Write a clear and concise summary of the project's purpose, main technologies, and architecture.
-*   **Building and Running:** Document the key commands for building, running, and testing the project. Infer these from the files you've read (e.g., \`scripts\` in \`package.json\`, \`Makefile\`, etc.). If you can't find explicit commands, provide a placeholder with a TODO.
-*   **Development Conventions:** Describe any coding styles, testing practices, or contribution guidelines you can infer from the codebase.
-
-**For a Non-Code Project:**
-
-*   **Directory Overview:** Describe the purpose and contents of the directory. What is it for? What kind of information does it hold?
-*   **Key Files:** List the most important files and briefly explain what they contain.
-*   **Usage:** Explain how the contents of this directory are intended to be used.
-
-**Final Output:**
-
-Write the complete content to the \`${contextFileName}\` file. The output must be well-formatted Markdown.
-`,
-    };
-  },
-};