block m4a uploads temporarily due to processing error

[spashii]

Summary by CodeRabbit

• New Features
  • Expanded file upload support to include additional audio and video formats, offering more flexibility.
• Bug Fixes
  • Improved error messaging for file upload rejections by switching to a more direct alert method, ensuring clearer user feedback.

[coderabbitai]

Walkthrough

This pull request updates the UploadConversationDropzone component in the frontend. The changes remove the dependency on toast.error by replacing it with the native alert in the error handling flow. Furthermore, the accepted file types have been modified—removing "audio/m4a" and "audio/x-m4a", while adding "audio/ogg", "audio/webm", and "video/mp4". There are no changes to the exported or public entities.

Changes

File	Changes Summary
echo/…/UploadConversationDropzone.tsx	Removed toast import and replaced toast.error with alert in the rejection callback; updated accepted file types (removed m4a, added ogg, webm, mp4)

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant D as Dropzone
    participant A as Alert

    U->>D: Drop file into component
    D->>D: Validate file types
    alt File type rejected
        D->>A: Call alert() with error message
    else File type accepted
        D->>D: Proceed with file handling
    end

Loading

Poem

In our code, a new path we pave,
Toasts give way to alerts so brave.
Formats shift with a swift embrace,
Files find their rightful place.
SF code, blazing the change!
🚀 LGTM!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f88e45c and 62df833.

📒 Files selected for processing (1)

• echo/frontend/src/components/dropzone/UploadConversationDropzone.tsx (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: ci-check-server

🔇 Additional comments (3)

echo/frontend/src/components/dropzone/UploadConversationDropzone.tsx (3)

16-16: Nice cleanup! Import toast killed.

You removed the toast import here. Super clean. Less dependencies = less problems.

---

40-43: Switched to native alert() - ship it!

Moving from toast.error to the native alert API. Smart move for blocking the UI when something goes wrong with uploads. Less dependencies and gives user no choice but to acknowledge the error. 10x efficiency gain.

---

49-52: Expanding codec support. Just-right file format mix.

• Block m4a ✅
• Add ogg/webm/mp4 ✅
• Keeping the standards ✅

Perfect codec strategy. Supporting the right formats improves UX while blocking problematic m4a files as requested in PR title.

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.