Skip to content

Conversation

@viral-shingadia
Copy link

Fixes Issue

Closes #58
Fixes incorrect error messages for unsupported and blank CSV uploads.

Changes proposed

  • Added validation for empty CSV files
  • Removed duplicate toast messages on the frontend when API returns errors
  • Improved error handling logic to avoid showing multiple errors for a single failure

Note to reviewers

  • This PR ensures that users receive clear, friendly error messages
    instead of raw backend responses (like 400/404).
  • Duplicate toast issues are now resolved.
  • Please verify both cases:
    1. Uploading an unsupported file type
    2. Uploading an empty CSV file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Raw API response displayed when user uploads unsupported/corrupted or empty file instead of user-friendly error

1 participant