ai-cli-mcp 2.19.0 → 2.20.1

package/dist/__tests__/model-alias.test.js

@@ -1,36 +0,0 @@
-import { describe, it, expect } from 'vitest';
-// Test the model alias resolution logic directly
-describe('Model Alias Resolution', () => {
-    // Define the same MODEL_ALIASES as in server.ts
-    const MODEL_ALIASES = {
-        'haiku': 'claude-3-5-haiku-20241022'
-    };
-    // Replicate the resolveModelAlias function
-    function resolveModelAlias(model) {
-        return MODEL_ALIASES[model] || model;
-    }
-    it('should resolve haiku alias to full model name', () => {
-        expect(resolveModelAlias('haiku')).toBe('claude-3-5-haiku-20241022');
-    });
-    it('should pass through non-alias model names unchanged', () => {
-        expect(resolveModelAlias('sonnet')).toBe('sonnet');
-        expect(resolveModelAlias('opus')).toBe('opus');
-        expect(resolveModelAlias('claude-3-opus-20240229')).toBe('claude-3-opus-20240229');
-    });
-    it('should pass through empty strings', () => {
-        expect(resolveModelAlias('')).toBe('');
-    });
-    it('should be case-sensitive', () => {
-        // Should not resolve uppercase version
-        expect(resolveModelAlias('Haiku')).toBe('Haiku');
-        expect(resolveModelAlias('HAIKU')).toBe('HAIKU');
-    });
-    it('should handle undefined input gracefully', () => {
-        // TypeScript would normally prevent this, but testing for runtime safety
-        expect(resolveModelAlias(undefined)).toBe(undefined);
-    });
-    it('should handle null input gracefully', () => {
-        // TypeScript would normally prevent this, but testing for runtime safety
-        expect(resolveModelAlias(null)).toBe(null);
-    });
-});