Fix: Validate empty file paths in file processing

[dipampaul17]

Fix: Validate empty file paths in file processing

Problem

When empty file paths are provided in actions like GMAIL_SEND_EMAIL, the application throws cryptic ENOENT errors instead of providing clear validation messages. This creates a poor developer experience and makes debugging difficult.

Solution

This PR adds proper validation for empty file paths at three critical points in the codebase:

1. In readFileContent function (fileUtils.ts):

if (!path || path.trim() === '') {
  throw new Error('File path cannot be empty');
}
In getFileDataAfterUploadingToS3 function (fileUtils.ts):
typescript
CopyInsert
if (!path || path.trim() === '') {
  throw new Error('File path cannot be empty');
}
In processFileUpload function (file.ts):
typescript
CopyInsert
const filePath = value as string;
if (!filePath || filePath.trim() === '') {
  throw new Error('File path cannot be empty');
}

These validations ensure that empty or whitespace-only file paths are caught early with clear error messages, preventing the cryptic ENOENT errors that would occur when attempting to read empty file paths.

Testing
End-to-end testing has been performed using the project's testing framework. All tests pass successfully, confirming that:

Empty paths are properly validated and throw the expected error
Whitespace-only paths are properly detected
The validation occurs at all critical points in the file processing workflow
Related Issue
Fixes #1578

@utkarsh-dixit

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
composio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 12, 2025 4:04am

[entelligence-ai-pr-reviews]

LGTM 👍