Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update useCreateEvent hook to handle photo library image URIs #387

Merged
merged 1 commit into from
Jan 14, 2025

Conversation

jaronheard
Copy link
Owner

@jaronheard jaronheard commented Jan 14, 2025

Summary by CodeRabbit

  • New Features

    • Enhanced photo library image selection and processing for event creation
    • Improved URI handling for images selected from device photo library
  • Bug Fixes

    • Fixed potential issues with image URI processing during event creation

Copy link

vercel bot commented Jan 14, 2025

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

1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
soonlist-turbo ⬜️ Skipped (Inspect) Jan 14, 2025 11:17am

Copy link

linear bot commented Jan 14, 2025

Copy link
Contributor

coderabbitai bot commented Jan 14, 2025

Walkthrough

The pull request modifies the useCreateEvent hook in the Expo application to improve handling of image URIs from the photo library. The changes introduce a mechanism to process photo library URIs by extracting the asset ID, retrieving the local file URI using MediaLibrary.getAssetInfoAsync, and ensuring the correct file path is used for image manipulation and uploading.

Changes

File Change Summary
apps/expo/src/hooks/useCreateEvent.ts - Added import for MediaLibrary from expo-media-library
- Implemented logic to handle photo library URIs starting with "ph://"
- Added asset ID extraction and local URI retrieval
- Updated image URI validation and processing flow

Sequence Diagram

sequenceDiagram
    participant User
    participant Hook as useCreateEvent
    participant MediaLib as MediaLibrary
    
    User->>Hook: Provide image URI
    alt Photo Library URI
        Hook->>MediaLib: getAssetInfoAsync(assetId)
        MediaLib-->>Hook: Return local file URI
    else Regular URI
        Hook->>Hook: Use original URI
    end
    Hook->>Hook: Validate and process image
Loading

Possibly related PRs

Finishing Touches

  • 📝 Generate Docstrings (Beta)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 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. (Beta)
  • @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.

@coderabbitai coderabbitai bot changed the title @coderabbitai Update useCreateEvent hook to handle photo library image URIs Jan 14, 2025
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🔭 Outside diff range comments (1)
apps/expo/src/hooks/useCreateEvent.ts (1)

Line range hint 134-139: Move API configuration to environment variables.

The Bytescale API endpoint and authorization token should be moved to environment variables for better security and configuration management.

+const UPLOAD_API_URL = process.env.UPLOAD_API_URL ?? "https://api.bytescale.com/v2/accounts/12a1yek/uploads/binary";
+const UPLOAD_API_KEY = process.env.UPLOAD_API_KEY ?? "public_12a1yekATNiLj4VVnREZ8c7LM8V8";

 response = await FileSystem.uploadAsync(
-  "https://api.bytescale.com/v2/accounts/12a1yek/uploads/binary",
+  UPLOAD_API_URL,
   manipulatedImage.uri,
   {
     uploadType: FileSystem.FileSystemUploadType.BINARY_CONTENT,
     httpMethod: "POST",
     headers: {
       "Content-Type": "image/jpeg",
-      Authorization: "Bearer public_12a1yekATNiLj4VVnREZ8c7LM8V8",
+      Authorization: `Bearer ${UPLOAD_API_KEY}`,
     },
   },
 );
🧹 Nitpick comments (3)
apps/expo/src/hooks/useCreateEvent.ts (3)

89-92: Consider making the asset ID extraction more robust.

The current implementation assumes a specific URI format. Consider adding more validation or using a URL parsing utility to handle potential variations in the URI format.

-const assetId = imageUri.replace("ph://", "").split("/")[0];
+const assetId = new URL(imageUri.replace("ph://", "https://")).pathname.split("/")[0];

111-111: Consider adding file cleanup.

After successful upload, consider cleaning up the temporary manipulated image file to free up device storage.

 // 4. Create event
+try {
   const result = (await eventFromImage.mutateAsync({
     imageUrl: fileUrl,
     // ... other props
   })) as CreateEventResult;
+  // Clean up temporary file
+  if (manipulatedImage?.uri.startsWith('file://')) {
+    await FileSystem.deleteAsync(manipulatedImage.uri, { idempotent: true });
+  }
   return result.eventId;
+} catch (error) {
+  // Clean up on error too
+  if (manipulatedImage?.uri.startsWith('file://')) {
+    await FileSystem.deleteAsync(manipulatedImage.uri, { idempotent: true });
+  }
+  throw error;
+}

108-114: Add file size validation before manipulation.

Consider adding a file size check before proceeding with image manipulation to prevent processing of extremely large files.

+const MAX_FILE_SIZE = 10 * 1024 * 1024; // 10MB

 // 1. Manipulate image
 let manipulatedImage;
 try {
+  const fileInfo = await FileSystem.getInfoAsync(fileUri);
+  if (fileInfo.size && fileInfo.size > MAX_FILE_SIZE) {
+    throw new Error(`File size exceeds ${MAX_FILE_SIZE / (1024 * 1024)}MB limit`);
+  }
   manipulatedImage = await ImageManipulator.manipulateAsync(
     fileUri,
     [{ resize: { width: 1284 } }],
     { compress: 0.8, format: ImageManipulator.SaveFormat.JPEG },
   );
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 9f281ee and ed94757.

📒 Files selected for processing (1)
  • apps/expo/src/hooks/useCreateEvent.ts (2 hunks)
🔇 Additional comments (1)
apps/expo/src/hooks/useCreateEvent.ts (1)

4-4: LGTM! Import statement follows the established pattern.

The import follows the same pattern as other expo-related imports in the file.

apps/expo/src/hooks/useCreateEvent.ts Show resolved Hide resolved
@jaronheard jaronheard merged commit d5bad9a into main Jan 14, 2025
7 of 8 checks passed
@jaronheard jaronheard deleted the jaronheard/tim-825-photo-loading branch January 14, 2025 11:20
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.

1 participant