The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
docs	Skipped			Dec 11, 2025 4:39am

Greptile Overview

Greptile Summary

This PR fixes multiple issues across Zendesk tools, knowledge base uploads, and WordPress integrations, while improving type definitions throughout.

Key Changes

• Knowledge Base MD Upload Fix: Browsers send empty content types for .md files, causing upload failures. Fixed by implementing getFileContentType helper that falls back to extension-based MIME type lookup when file.type is empty. Both client-side (use-knowledge-upload.ts) and server-side (validation.ts) now handle empty MIME types gracefully.

• Zendesk Tool Output Typing: Flattened output structure across all 26 Zendesk tools by removing redundant nested success and output wrappers. Updated block config to define operation-specific outputs (ticket, tickets, user, users, organization, organizations, results, count, jobStatus, deleted, paging, metadata) instead of generic success/output fields.

• WordPress Upload Route: Added /api/tools/wordpress/upload route to align with other tool patterns (download/upload architecture). Tool now uses file type instead of string for better type safety, and block UI provides both file-upload component and variable reference modes.

• Tag Dropdown Icons: Fixed icon display by supporting React component icons (RepeatIcon, SplitIcon) in addition to letter-based icons. Now uses actual block icons when available, falling back to special icons for loop/parallel blocks.

• YouTube Tool Cleanup: Removed related_videos tool and its references.

Issues Found

• Code duplication: getMimeType function in apps/sim/app/api/tools/wordpress/upload/route.ts duplicates existing getMimeTypeFromExtension from @/lib/uploads/utils/file-utils

Confidence Score: 4/5

• This PR is safe to merge with minor code duplication that should be addressed
• The changes are well-structured and address real bugs (MD file uploads, Zendesk typing). The implementations are sound with proper error handling and logging. Score reduced by 1 point due to code duplication in the WordPress route that should use existing utilities.
• apps/sim/app/api/tools/wordpress/upload/route.ts has code duplication that should use existing utilities

Important Files Changed

File Analysis

Sequence Diagram

sequenceDiagram
    participant User
    participant Browser
    participant KBUploadHook as Knowledge Upload Hook
    participant ValidationUtils as Validation Utils
    participant FileUtils as File Utils
    participant S3 as S3 Storage

    Note over User,S3: MD File Upload Flow (Fixed)
    
    User->>Browser: Select .md file
    Browser->>KBUploadHook: File object (empty type)
    KBUploadHook->>KBUploadHook: getFileContentType(file)
    alt file.type is empty
        KBUploadHook->>FileUtils: getFileExtension(filename)
        FileUtils-->>KBUploadHook: "md"
        KBUploadHook->>FileUtils: getMimeTypeFromExtension("md")
        FileUtils-->>KBUploadHook: "text/markdown"
    else file.type exists
        KBUploadHook->>KBUploadHook: Use file.type
    end
    
    KBUploadHook->>ValidationUtils: validateFileType(filename, mimeType)
    ValidationUtils->>ValidationUtils: Check if baseMimeType is empty
    alt baseMimeType is empty
        ValidationUtils-->>KBUploadHook: null (allow)
    else baseMimeType exists
        ValidationUtils->>ValidationUtils: Validate against allowed types
        ValidationUtils-->>KBUploadHook: null or error
    end
    
    KBUploadHook->>S3: Upload with derived MIME type
    S3-->>KBUploadHook: Success
    KBUploadHook-->>User: File uploaded

    Note over User,S3: WordPress Upload Flow (New Route)
    
    User->>Browser: Select media file
    Browser->>WordPressTool: File via tool
    WordPressTool->>APIRoute: POST /api/tools/wordpress/upload
    APIRoute->>APIRoute: processSingleFileToUserFile
    APIRoute->>APIRoute: downloadFileFromStorage
    APIRoute->>APIRoute: getMimeType (extension-based)
    APIRoute->>WordPress: FormData with file
    WordPress-->>APIRoute: Media object
    APIRoute-->>WordPressTool: Success response
    WordPressTool-->>User: Media uploaded