Exclude .DS_Store files, run prettier

Author: osolmaz

.eslintrc.js

@@ -1,28 +1,25 @@
 module.exports = {
-  parser: '@typescript-eslint/parser',
-  extends: [
-    'eslint:recommended',
-    'plugin:@typescript-eslint/recommended'
-  ],
+  parser: "@typescript-eslint/parser",
+  extends: ["eslint:recommended", "plugin:@typescript-eslint/recommended"],
   parserOptions: {
     ecmaVersion: 2022,
-    sourceType: 'module',
-    project: './tsconfig.json'
+    sourceType: "module",
+    project: "./tsconfig.json",
   },
   env: {
     node: true,
     es2022: true,
-    jest: true
+    jest: true,
   },
-  plugins: ['@typescript-eslint'],
+  plugins: ["@typescript-eslint"],
   rules: {
-    '@typescript-eslint/explicit-module-boundary-types': 'off',
-    '@typescript-eslint/no-explicit-any': 'warn',
-    '@typescript-eslint/no-unused-vars': ['error', { argsIgnorePattern: '^_' }],
-    'no-console': 'off',
-    'semi': ['error', 'always'],
-    'quotes': ['error', 'single'],
-    'comma-dangle': ['error', 'never']
+    "@typescript-eslint/explicit-module-boundary-types": "off",
+    "@typescript-eslint/no-explicit-any": "warn",
+    "@typescript-eslint/no-unused-vars": ["error", { argsIgnorePattern: "^_" }],
+    "no-console": "off",
+    semi: ["error", "always"],
+    quotes: ["error", "single"],
+    "comma-dangle": ["error", "never"],
   },
-  ignorePatterns: ['dist/', 'node_modules/', 'coverage/', '*.js']
-};
+  ignorePatterns: ["dist/", "node_modules/", "coverage/", "*.js"],
+};

TODO.md

@@ -12,4 +12,4 @@
   - a. Let user merge changes from remote to local: We would need to implement a conflict resolver somehow.
   - b. If conflicts arise, we could just block the operation and let user dump the current state in order not to lose work. This is the simplest option.
   - Either way, we need to think about how to apply new commits from the remote, because changes currently only flow from the sandbox to the shadow repo.
-- [ ] rsync, inotifywait, etc. should be included in the image, not installed in the fly
+- [ ] rsync, inotifywait, etc. should be included in the image, not installed in the fly

docs/git-operations-plan.md

@@ -39,6 +39,7 @@ This plan outlines how to safely handle Git operations (commit, push, PR) outsid
    ```
 
 2. **Shadow Repository Setup (Optimized)**
+
    ```typescript
    class ShadowRepository {
      private shadowPath: string;

jest.config.js

@@ -1,39 +1,36 @@
 module.exports = {
-  preset: 'ts-jest',
-  testEnvironment: 'node',
-  roots: ['<rootDir>/test'],
+  preset: "ts-jest",
+  testEnvironment: "node",
+  roots: ["<rootDir>/test"],
   testMatch: [
-    '**/test/**/*.test.ts',
-    '**/test/**/*.test.js',
-    '**/test/**/*.spec.ts',
-    '**/test/**/*.spec.js'
+    "**/test/**/*.test.ts",
+    "**/test/**/*.test.js",
+    "**/test/**/*.spec.ts",
+    "**/test/**/*.spec.js",
   ],
-  moduleFileExtensions: ['ts', 'tsx', 'js', 'jsx', 'json', 'node'],
+  moduleFileExtensions: ["ts", "tsx", "js", "jsx", "json", "node"],
   transform: {
-    '^.+\\.tsx?$': 'ts-jest',
-    '^.+\\.jsx?$': 'babel-jest'
+    "^.+\\.tsx?$": "ts-jest",
+    "^.+\\.jsx?$": "babel-jest",
   },
   collectCoverageFrom: [
-    'src/**/*.{ts,tsx}',
-    '!src/**/*.d.ts',
-    '!src/**/*.test.{ts,tsx}',
-    '!src/**/*.spec.{ts,tsx}'
-  ],
-  coverageDirectory: '<rootDir>/coverage',
-  coverageReporters: ['text', 'lcov', 'html'],
-  testPathIgnorePatterns: [
-    '/node_modules/',
-    '/dist/'
+    "src/**/*.{ts,tsx}",
+    "!src/**/*.d.ts",
+    "!src/**/*.test.{ts,tsx}",
+    "!src/**/*.spec.{ts,tsx}",
   ],
+  coverageDirectory: "<rootDir>/coverage",
+  coverageReporters: ["text", "lcov", "html"],
+  testPathIgnorePatterns: ["/node_modules/", "/dist/"],
   moduleNameMapper: {
-    '^@/(.*)$': '<rootDir>/src/$1'
+    "^@/(.*)$": "<rootDir>/src/$1",
   },
   globals: {
-    'ts-jest': {
+    "ts-jest": {
       tsconfig: {
         esModuleInterop: true,
-        allowJs: true
-      }
-    }
-  }
-};
+        allowJs: true,
+      },
+    },
+  },
+};

src/container.ts

@@ -573,11 +573,14 @@ exec claude --dangerously-skip-permissions' > /start-claude.sh && \\
       // Also copy .git directory to preserve git history
       console.log(chalk.blue("• Copying git history..."));
       const gitTarFile = `/tmp/claude-sandbox-git-${Date.now()}.tar`;
-      // Exclude macOS resource fork files when creating git archive
-      execSync(`tar -cf "${gitTarFile}" --exclude="._*" .git`, {
-        cwd: workDir,
-        stdio: "pipe",
-      });
+      // Exclude macOS resource fork files and .DS_Store when creating git archive
+      execSync(
+        `tar -cf "${gitTarFile}" --exclude="._*" --exclude=".DS_Store" .git`,
+        {
+          cwd: workDir,
+          stdio: "pipe",
+        },
+      );
 
       try {
         const gitStream = fs.createReadStream(gitTarFile);

src/git/shadow-repository.ts

@@ -166,9 +166,12 @@ export class ShadowRepository {
       try {
         await execAsync("git add .", { cwd: this.shadowPath });
         console.log(chalk.gray("  Staged all files for tracking"));
-        
+
         // Create initial commit to ensure deletions can be tracked
-        await execAsync('git commit -m "Initial snapshot of working directory" --allow-empty', { cwd: this.shadowPath });
+        await execAsync(
+          'git commit -m "Initial snapshot of working directory" --allow-empty',
+          { cwd: this.shadowPath },
+        );
         console.log(chalk.gray("  Created initial commit for change tracking"));
       } catch (stageError: any) {
         console.log(chalk.gray("  Could not stage files:", stageError.message));
@@ -426,8 +429,10 @@ export class ShadowRepository {
 
     // Rsync directly from container to shadow repo with proper deletion handling
     // First, clear the shadow repo (except .git) to ensure deletions are reflected
-    await execAsync(`find ${this.shadowPath} -mindepth 1 -not -path '${this.shadowPath}/.git*' -delete`);
-    
+    await execAsync(
+      `find ${this.shadowPath} -mindepth 1 -not -path '${this.shadowPath}/.git*' -delete`,
+    );
+
     // Rsync within container to staging area using exclude file
     const rsyncCmd = `docker exec ${containerId} rsync -av --delete \
       --exclude-from=${containerExcludeFile} \

test/README.md

@@ -48,22 +48,23 @@ Tests are written using Jest with TypeScript support. The Jest configuration is
 ### Example Unit Test
 
 ```typescript
-import { someFunction } from '../../src/someModule';
+import { someFunction } from "../../src/someModule";
 
-describe('someFunction', () => {
-  it('should do something', () => {
-    const result = someFunction('input');
-    expect(result).toBe('expected output');
+describe("someFunction", () => {
+  it("should do something", () => {
+    const result = someFunction("input");
+    expect(result).toBe("expected output");
   });
 });
 ```
 
 ## E2E Tests
 
 End-to-end tests are located in `test/e2e/` and test the complete workflow of the CLI tool. These tests:
+
 - Create actual Docker containers
 - Run Claude commands
 - Verify git operations
 - Test the full user experience
 
-Run E2E tests with: `npm run test:e2e`
+Run E2E tests with: `npm run test:e2e`

test/e2e/README.md

@@ -35,12 +35,14 @@ The tests create a temporary git repository, start a claude-sandbox instance, pe
 ## Running Tests
 
 ### Quick Test (Recommended)
+
 ```bash
 # Run core functionality tests
 node core-functionality-test.js
 ```
 
 ### Individual Tests
+
 ```bash
 # Test repository to container sync
 node repo-to-container-sync-test.js
@@ -53,6 +55,7 @@ node test-suite.js
 ```
 
 ### Automated Test Runner
+
 ```bash
 # Run all tests with cleanup
 ./run-tests.sh
@@ -67,11 +70,13 @@ node test-suite.js
 ## Test Process
 
 1. **Setup Phase**
+
    - Creates temporary git repository with dummy files
    - Starts claude-sandbox instance
    - Connects to web UI for monitoring sync events
 
 2. **Test Execution**
+
    - Performs file operations inside the container
    - Waits for synchronization to complete
    - Verifies shadow repository state
@@ -84,13 +89,15 @@ node test-suite.js
 ## Key Features Tested
 
 ### Repository to Container Sync
+
 - ✅ One-to-one file mapping from test repo to container
 - ✅ No extra files in container (only test repo files)
 - ✅ File content integrity verification
 - ✅ Git repository properly initialized
 - ✅ Correct branch creation
 
 ### File Synchronization
+
 - ✅ New file creation and content sync
 - ✅ File modification and content updates
 - ✅ File deletion and proper removal
@@ -99,12 +106,14 @@ node test-suite.js
 - ✅ Special characters in filenames
 
 ### Git Integration
+
 - ✅ Staging of additions (`A` status)
 - ✅ Tracking of modifications (`M` status)
 - ✅ Detection of deletions (`D` status)
 - ✅ Proper git commit workflow
 
 ### Web UI Integration
+
 - ✅ Real-time sync event notifications
 - ✅ Change summary reporting
 - ✅ WebSocket communication
@@ -114,25 +123,30 @@ node test-suite.js
 ### Common Issues
 
 **Container startup timeout**
+
 - Increase timeout values in test framework
 - Check Docker daemon is running
 - Verify claude-sandbox image exists
 
 **Git lock conflicts**
+
 - Tests automatically handle concurrent git operations
 - Temporary `.git/index.lock` files are cleaned up
 
 **Port conflicts**
+
 - Tests use dynamic port allocation
 - Multiple tests can run sequentially
 
 **WebSocket connection issues**
+
 - Framework includes connection retry logic
 - Fallback to polling if WebSocket fails
 
 ### Test Failure Analysis
 
 Tests provide detailed error messages indicating:
+
 - Which specific operation failed
 - Expected vs actual file states
 - Git status differences
@@ -145,33 +159,36 @@ Tests provide detailed error messages indicating:
 1. Create test function in appropriate test file
 2. Use framework methods for file operations:
    ```javascript
-   await framework.addFile('path/file.txt', 'content');
-   await framework.modifyFile('path/file.txt', 'new content');
-   await framework.deleteFile('path/file.txt');
+   await framework.addFile("path/file.txt", "content");
+   await framework.modifyFile("path/file.txt", "new content");
+   await framework.deleteFile("path/file.txt");
    ```
 3. Verify results using assertion methods:
    ```javascript
-   const exists = await framework.shadowFileExists('file.txt');
-   const content = await framework.getShadowFileContent('file.txt');
+   const exists = await framework.shadowFileExists("file.txt");
+   const content = await framework.getShadowFileContent("file.txt");
    const gitStatus = await framework.getGitStatus();
    ```
 
 ### Framework API
 
 **File Operations**
+
 - `addFile(path, content)` - Create new file
-- `modifyFile(path, content)` - Update existing file  
+- `modifyFile(path, content)` - Update existing file
 - `deleteFile(path)` - Remove file
 - `moveFile(from, to)` - Rename/move file
 - `createDirectory(path)` - Create directory
 
 **Verification Methods**
+
 - `shadowFileExists(path)` - Check file existence
 - `getShadowFileContent(path)` - Read file content
 - `getGitStatus()` - Get git status output
 - `waitForSync()` - Wait for synchronization
 
 **Event Monitoring**
+
 - `receivedSyncEvents` - Array of sync notifications
 - WebSocket connection automatically established
 
@@ -188,4 +205,4 @@ These tests are designed to run in automated environments:
     ./run-tests.sh
 ```
 
-The tests provide proper exit codes (0 for success, 1 for failure) and detailed logging for debugging purposes.
+The tests provide proper exit codes (0 for success, 1 for failure) and detailed logging for debugging purposes.