feat(fe): save profile image to pinata

[dungpt99]

Summary by CodeRabbit

• New Features

  • Uploaded profile images are now stored on IPFS via Pinata, providing a secure, decentralized image URL preview instead of a local base64 preview.

• Bug Fixes

  • Improved error handling for image uploads, with error notifications if the upload fails.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The image upload logic in the BasicInformationForm component was refactored from using a local base64 encoding approach to uploading images asynchronously to Pinata's IPFS service. The handler now sends the file to Pinata, retrieves the resulting IPFS URL, and updates the form with this remote image link.

Changes

File(s)	Change Summary
frontend/src/components/BasicInformationForm.tsx	Refactored image upload logic to use Pinata IPFS service via async POST request; updated handler signature to async; now sets image preview and form field to IPFS URL instead of base64 string.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant BasicInformationForm
    participant PinataAPI

    User->>BasicInformationForm: Selects image file (input change)
    BasicInformationForm->>PinataAPI: POST file to Pinata (with JWT)
    PinataAPI-->>BasicInformationForm: Returns IPFS hash (or error)
    BasicInformationForm->>BasicInformationForm: Construct IPFS URL, set as preview & form value

Loading

Poem

A bunny hops with code anew,
Now images leap to IPFS too!
No more base64, but hashes that gleam,
Pinata holds the picture dream.
Async we go, with uploads that fly—
Carrots for code, and clouds in the sky! 🥕✨

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
curatedotfun-app	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 20, 2025 5:04am

[elliotBraem]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Actionable comments posted: 2

🔭 Outside diff range comments (1)

frontend/src/components/BasicInformationForm.tsx (1)

1-227: 💡 Verification agent

🧩 Analysis chain

Fix the Prettier formatting issues

The CI pipeline reported Prettier formatting issues in this file.

---

🏁 Script executed:

#!/bin/bash
# Run Prettier to check formatting issues in the file
npx prettier --check frontend/src/components/BasicInformationForm.tsx

Length of output: 322

---

Fix Prettier formatting in BasicInformationForm.tsx

Prettier has detected code style issues in this file. To resolve, run:

npx prettier --write frontend/src/components/BasicInformationForm.tsx

Then review and commit the updated formatting.

🧰 Tools

🪛 GitHub Actions: CI

[warning] 1-1: Prettier formatting check failed. Run Prettier with --write to fix code style issues.

🧹 Nitpick comments (2)

frontend/src/components/BasicInformationForm.tsx (2)

64-64: Add file validation before uploading

The code doesn't validate the file type, size, or dimensions before uploading, which could lead to issues with inappropriate files or very large files.

Add validation for file type, size, and dimensions before uploading:

    const file = event.target.files?.[0];
    if (file) {
+     // Validate file type
+     const validTypes = ['image/jpeg', 'image/png', 'image/gif'];
+     if (!validTypes.includes(file.type)) {
+       console.error('Invalid file type');
+       toast({
+         title: "Invalid file type",
+         description: "Please upload a JPEG, PNG, or GIF image.",
+         variant: "destructive",
+       });
+       return;
+     }
+     
+     // Validate file size (5MB max)
+     const maxSize = 5 * 1024 * 1024; // 5MB
+     if (file.size > maxSize) {
+       console.error('File too large');
+       toast({
+         title: "File too large",
+         description: "Please upload an image smaller than 5MB.",
+         variant: "destructive",
+       });
+       return;
+     }
      try {

---

82-82: Consider using a more resilient IPFS gateway strategy

Using a single public IPFS gateway (ipfs.io) may lead to availability issues if that gateway experiences high load or downtime.

Consider implementing a more resilient gateway strategy:

-       const ipfsUrl = `https://ipfs.io/ipfs/${data.IpfsHash}`;
+       // Use Pinata's dedicated gateway or allow configuration
+       const gateway = import.meta.env.PUBLIC_IPFS_GATEWAY || 'https://ipfs.io';
+       const ipfsUrl = `${gateway}/ipfs/${data.IpfsHash}`;

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between cdf9a14 and e767e7f.

📒 Files selected for processing (1)

• frontend/src/components/BasicInformationForm.tsx (1 hunks)

🧰 Additional context used

🪛 GitHub Actions: CI

frontend/src/components/BasicInformationForm.tsx

[warning] 1-1: Prettier formatting check failed. Run Prettier with --write to fix code style issues.

[coderabbitai]

🛠️ Refactor suggestion

Verify environment variable availability before using it

The code assumes that PUBLIC_PINATA_JWT_KEY is defined in the environment. If it's missing, this will cause runtime errors.

Add a check to ensure the environment variable is defined:

        const response = await fetch('https://api.pinata.cloud/pinning/pinFileToIPFS', {
          method: 'POST',
          headers: {
-           Authorization: `Bearer ${import.meta.env.PUBLIC_PINATA_JWT_KEY}`,
+           Authorization: `Bearer ${import.meta.env.PUBLIC_PINATA_JWT_KEY || ''}`,
          },
          body: formData,
        });

+       if (!import.meta.env.PUBLIC_PINATA_JWT_KEY) {
+         throw new Error('Pinata JWT key is not configured');
+       }

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents

In frontend/src/components/BasicInformationForm.tsx at line 72, the code uses
the environment variable PUBLIC_PINATA_JWT_KEY without verifying its presence,
which can cause runtime errors if it's undefined. Add a check before using this
variable to confirm it is defined; if not, handle the missing case
appropriately, such as throwing an error or providing a fallback, to prevent
runtime failures.

[coderabbitai]

🛠️ Refactor suggestion

Good implementation of Pinata IPFS integration, but needs better error handling for users

The conversion from a local base64 approach to using Pinata's IPFS service is a good improvement for scalability. However, the current implementation only logs errors to the console without providing any feedback to users when uploads fail.

Consider adding user feedback for upload failures:

  const handleImageUpload = async (event: React.ChangeEvent<HTMLInputElement>) => {
    const file = event.target.files?.[0];
    if (file) {
+     const [isUploading, setIsUploading] = useState(false);
      try {
+       setIsUploading(true);
        const formData = new FormData();
        formData.append('file', file);

        const response = await fetch('https://api.pinata.cloud/pinning/pinFileToIPFS', {
          method: 'POST',
          headers: {
            Authorization: `Bearer ${import.meta.env.PUBLIC_PINATA_JWT_KEY}`,
          },
          body: formData,
        });

        if (!response.ok) {
          throw new Error('Failed to upload file to Pinata');
        }

        const data = await response.json();
        const ipfsUrl = `https://ipfs.io/ipfs/${data.IpfsHash}`;
        setImagePreview(ipfsUrl);
        form.setValue("profileImage", ipfsUrl);
      } catch (error) {
        console.error('Error uploading file to Pinata:', error);
+       // Show error to user
+       toast({
+         title: "Upload failed",
+         description: "Failed to upload image. Please try again.",
+         variant: "destructive",
+       });
      } finally {
+       setIsUploading(false);
      }
    }
  };

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents

In frontend/src/components/BasicInformationForm.tsx around lines 62 to 89, the
handleImageUpload function logs errors to the console but does not provide user
feedback on upload failures. Enhance the error handling by adding a user-visible
notification or message when the upload to Pinata fails, such as setting an
error state or displaying a toast alert, so users are informed of the failure
and can take appropriate action.