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

feat: "Feature Request: Bulk Image Upload Capability in Media Popup" #398

Closed
wants to merge 4 commits into from

Conversation

naaa760
Copy link

@naaa760 naaa760 commented Oct 25, 2024

What kind of change does this PR introduce?

Feature: Multi-image upload functionality in the media popup.

Why was this change needed?

Efficiency: Streamlines the post-creation process by allowing users to select multiple images simultaneously.
User Experience: Reduces the time spent uploading images, enhancing overall productivity.
Related Issue: Addresses #1234 - "Enhance media upload process for post creation."

Other information:

Discussion: Collaborated with the frontend team to ensure design consistency.
Future Plans: Gather user feedback for potential enhancements, including drag-and-drop support.

Summary by CodeRabbit

  • New Features
    • Introduced a media selection popup with intuitive visual cues to simplify choosing images.
    • Launched a new post creation interface that integrates easy image selection and preview.
    • Enhanced prompt handling in the configuration to minimize repetitive notifications.

Copy link

vercel bot commented Oct 25, 2024

Someone is attempting to deploy a commit to the Listinai Team on Vercel.

A member of the Team first needs to authorize it.

Copy link

@bsantosh909 bsantosh909 left a comment

Choose a reason for hiding this comment

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

Is this even related to the project by any means?? 🤔

@@ -0,0 +1,3 @@
{
"WillLuke.nextjs.hasPrompted": true
Copy link
Contributor

Choose a reason for hiding this comment

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

Please remove this file from the PR.

Copy link

@A1exKH A1exKH left a comment

Choose a reason for hiding this comment

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

@naaa760 please exclude this file from your PR ".vscode/settings.json".

Copy link

coderabbitai bot commented Feb 4, 2025

Walkthrough

This pull request introduces a new VS Code setting in .vscode/settings.json to track whether a Next.js prompt has been acknowledged. Additionally, it adds two new React components in the frontend. The first component, MediaPopup, provides an interface for image selection with toggle functionality and a confirmation button. The second component, PostCreator, utilizes MediaPopup to enable users to create posts with selected images. Both components manage their respective states and interactions while maintaining clear component boundaries.

Changes

File(s) Change Summary
.vscode/settings.json Added key "WillLuke.nextjs.hasPrompted": true to record that the Next.js prompt has been displayed.
apps/frontend/src/components/MediaPopup.tsx, apps/frontend/src/components/PostCreator.tsx Introduced two new React components: MediaPopup (for image selection with toggle and confirmation) and PostCreator (for managing post creation including image gallery and state management).

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant PC as PostCreator
    participant MP as MediaPopup

    U->>PC: Click "Add Images" button
    PC->>MP: Open MediaPopup with image gallery
    U->>MP: Click to select/deselect images
    MP->>U: Update selection feedback
    U->>MP: Confirm selection with "Add Images" button
    MP->>PC: Return selected images
    PC->>U: Display updated image list in the post
Loading

Poem

In a meadow of code I hop with glee,
New settings and components set me free.
MediaPopup dances with images bright,
PostCreator guides posts into the light.
I’m a coding bunny, nimble and keen,
Leaping through updates with a joyful sheen!
🐰✨

Tip

🌐 Web search-backed reviews and chat
  • We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
  • You can disable this feature by setting web_search: false in the knowledge_base settings.
  • Please share any feedback in the Discord discussion.

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.

}`}
onClick={() => toggleImageSelection(image)}
>
<img src={image} alt="media" />

Check warning

Code scanning / ESLint

Prevent usage of `<img>` element due to slower LCP and higher bandwidth. Warning

Using <img> could result in slower LCP and higher bandwidth. Consider using <Image /> from next/image to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
Comment on lines +30 to +35
<img
key={image}
src={image}
alt="Selected"
className="selected-image"
/>

Check warning

Code scanning / ESLint

Prevent usage of `<img>` element due to slower LCP and higher bandwidth. Warning

Using <img> could result in slower LCP and higher bandwidth. Consider using <Image /> from next/image to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
Copy link

@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: 3

🧹 Nitpick comments (4)
apps/frontend/src/components/PostCreator.tsx (2)

8-14: Consider loading image gallery data dynamically.

The imageGallery array is currently hardcoded with static image paths. Consider loading this data dynamically from an API or configuration file for better maintainability.

-  const imageGallery = [
-    'image1.jpg',
-    'image2.jpg',
-    'image3.jpg',
-    'image4.jpg',
-    // Add more image URLs or file paths here
-  ];
+  const [imageGallery, setImageGallery] = useState<string[]>([]);
+
+  useEffect(() => {
+    // Load images from API or configuration
+    const loadImages = async () => {
+      try {
+        const response = await fetch('/api/media/images');
+        const data = await response.json();
+        setImageGallery(data);
+      } catch (error) {
+        console.error('Failed to load images:', error);
+      }
+    };
+    loadImages();
+  }, []);

16-20: Consider adding error handling for image selection.

The handleAddImages callback should include error handling for cases where image selection fails or invalid images are selected.

   const handleAddImages = (images: string[]) => {
+    try {
+      // Validate images (e.g., check file types, sizes)
+      const validImages = images.filter(image => {
+        const extension = image.split('.').pop()?.toLowerCase();
+        return ['jpg', 'jpeg', 'png', 'gif'].includes(extension || '');
+      });
+
+      if (validImages.length !== images.length) {
+        console.warn('Some images were skipped due to invalid file types');
+      }
+
-      setSelectedImages((prevImages) => [...prevImages, ...images]);
+      setSelectedImages((prevImages) => [...prevImages, ...validImages]);
       setShowMediaPopup(false);
+    } catch (error) {
+      console.error('Failed to add images:', error);
+      // Handle error (e.g., show error message to user)
+    }
   };
apps/frontend/src/components/MediaPopup.tsx (2)

3-6: Consider adding additional props for customization.

The component could benefit from additional props for customization, such as:

  • Maximum number of selectable images
  • Custom styling options
  • Accessibility labels
 interface MediaPopupProps {
   images: string[];
   onAddImages: (selectedImages: string[]) => void;
+  maxSelectable?: number;
+  className?: string;
+  labels?: {
+    title?: string;
+    addButton?: string;
+  };
 }

11-24: Add maximum selection limit and selection order.

The image selection logic should include:

  • Maximum selection limit
  • Selection order tracking for better UX
-  const toggleImageSelection = (image: string) => {
+  const toggleImageSelection = (image: string) => {
+    const maxSelectable = props.maxSelectable || Infinity;
+
     if (selectedImages.includes(image)) {
       setSelectedImages(selectedImages.filter((img) => img !== image));
     } else {
+      if (selectedImages.length >= maxSelectable) {
+        // Show error message or handle max limit
+        return;
+      }
       setSelectedImages([...selectedImages, image]);
     }
   };
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 13585a1 and 99d4c3c.

📒 Files selected for processing (3)
  • .vscode/settings.json (1 hunks)
  • apps/frontend/src/components/MediaPopup.tsx (1 hunks)
  • apps/frontend/src/components/PostCreator.tsx (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • .vscode/settings.json
🧰 Additional context used
🪛 GitHub Check: ESLint
apps/frontend/src/components/PostCreator.tsx

[warning] 30-35: Prevent usage of <img> element due to slower LCP and higher bandwidth.
Using <img> could result in slower LCP and higher bandwidth. Consider using <Image /> from next/image to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

apps/frontend/src/components/MediaPopup.tsx

[warning] 38-38: Prevent usage of <img> element due to slower LCP and higher bandwidth.
Using <img> could result in slower LCP and higher bandwidth. Consider using <Image /> from next/image to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: build (20.17.0)

Comment on lines +29 to +36
{selectedImages.map((image) => (
<img
key={image}
src={image}
alt="Selected"
className="selected-image"
/>
))}
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Replace <img> with Next.js Image component for better performance.

Using the <img> element can result in slower LCP (Largest Contentful Paint) and higher bandwidth usage. Consider using Next.js's Image component for automatic image optimization.

+import Image from 'next/image';

-        {selectedImages.map((image) => (
-          <img
-            key={image}
-            src={image}
-            alt="Selected"
-            className="selected-image"
-          />
-        ))}
+        {selectedImages.map((image) => (
+          <Image
+            key={image}
+            src={image}
+            alt="Selected"
+            width={100}
+            height={100}
+            className="selected-image"
+            objectFit="cover"
+          />
+        ))}
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
{selectedImages.map((image) => (
<img
key={image}
src={image}
alt="Selected"
className="selected-image"
/>
))}
import Image from 'next/image';
// ... other imports and code above remain unchanged
{selectedImages.map((image) => (
<Image
key={image}
src={image}
alt="Selected"
width={100}
height={100}
className="selected-image"
objectFit="cover"
/>
))}
🧰 Tools
🪛 GitHub Check: ESLint

[warning] 30-35: Prevent usage of <img> element due to slower LCP and higher bandwidth.
Using <img> could result in slower LCP and higher bandwidth. Consider using <Image /> from next/image to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

}`}
onClick={() => toggleImageSelection(image)}
>
<img src={image} alt="media" />
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Replace <img> with Next.js Image component.

Similar to the previous file, replace the <img> element with Next.js's Image component for better performance.

+import Image from 'next/image';

-            <img src={image} alt="media" />
+            <Image
+              src={image}
+              alt="media"
+              width={100}
+              height={100}
+              objectFit="cover"
+            />
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<img src={image} alt="media" />
import Image from 'next/image';
...
<Image
src={image}
alt="media"
width={100}
height={100}
objectFit="cover"
/>
...
🧰 Tools
🪛 GitHub Check: ESLint

[warning] 38-38: Prevent usage of <img> element due to slower LCP and higher bandwidth.
Using <img> could result in slower LCP and higher bandwidth. Consider using <Image /> from next/image to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

Comment on lines +26 to +82
return (
<div className="media-popup">
<h3>Select Images</h3>
<div className="image-grid">
{images.map((image) => (
<div
key={image}
className={`image-item ${
selectedImages.includes(image) ? 'selected' : ''
}`}
onClick={() => toggleImageSelection(image)}
>
<img src={image} alt="media" />
</div>
))}
</div>
<button onClick={handleAddClick} disabled={selectedImages.length === 0}>
Add {selectedImages.length > 0 ? `(${selectedImages.length})` : ''}{' '}
Images
</button>

<style jsx>{`
.media-popup {
padding: 20px;
}
.image-grid {
display: grid;
grid-template-columns: repeat(auto-fill, minmax(100px, 1fr));
gap: 10px;
}
.image-item {
cursor: pointer;
border: 2px solid transparent;
transition: border-color 0.3s ease;
}
.image-item img {
max-width: 100px;
height: auto;
}
.image-item.selected {
border-color: blue; /* Border for selected images */
}
button {
margin-top: 20px;
padding: 10px;
background-color: #007bff;
color: white;
border: none;
cursor: pointer;
border-radius: 5px;
}
button:disabled {
background-color: grey;
cursor: not-allowed;
}
`}</style>
</div>
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Add keyboard navigation and accessibility features.

The component should support keyboard navigation and include proper ARIA attributes for better accessibility.

   return (
-    <div className="media-popup">
+    <div
+      className="media-popup"
+      role="dialog"
+      aria-labelledby="media-popup-title"
+    >
-      <h3>Select Images</h3>
+      <h3 id="media-popup-title">Select Images</h3>
       <div className="image-grid">
         {images.map((image) => (
           <div
             key={image}
             className={`image-item ${
               selectedImages.includes(image) ? 'selected' : ''
             }`}
             onClick={() => toggleImageSelection(image)}
+            onKeyDown={(e) => {
+              if (e.key === 'Enter' || e.key === ' ') {
+                toggleImageSelection(image);
+              }
+            }}
+            role="button"
+            tabIndex={0}
+            aria-pressed={selectedImages.includes(image)}
           >
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
return (
<div className="media-popup">
<h3>Select Images</h3>
<div className="image-grid">
{images.map((image) => (
<div
key={image}
className={`image-item ${
selectedImages.includes(image) ? 'selected' : ''
}`}
onClick={() => toggleImageSelection(image)}
>
<img src={image} alt="media" />
</div>
))}
</div>
<button onClick={handleAddClick} disabled={selectedImages.length === 0}>
Add {selectedImages.length > 0 ? `(${selectedImages.length})` : ''}{' '}
Images
</button>
<style jsx>{`
.media-popup {
padding: 20px;
}
.image-grid {
display: grid;
grid-template-columns: repeat(auto-fill, minmax(100px, 1fr));
gap: 10px;
}
.image-item {
cursor: pointer;
border: 2px solid transparent;
transition: border-color 0.3s ease;
}
.image-item img {
max-width: 100px;
height: auto;
}
.image-item.selected {
border-color: blue; /* Border for selected images */
}
button {
margin-top: 20px;
padding: 10px;
background-color: #007bff;
color: white;
border: none;
cursor: pointer;
border-radius: 5px;
}
button:disabled {
background-color: grey;
cursor: not-allowed;
}
`}</style>
</div>
return (
<div
className="media-popup"
role="dialog"
aria-labelledby="media-popup-title"
>
<h3 id="media-popup-title">Select Images</h3>
<div className="image-grid">
{images.map((image) => (
<div
key={image}
className={`image-item ${selectedImages.includes(image) ? 'selected' : ''}`}
onClick={() => toggleImageSelection(image)}
onKeyDown={(e) => {
if (e.key === 'Enter' || e.key === ' ') {
toggleImageSelection(image);
}
}}
role="button"
tabIndex={0}
aria-pressed={selectedImages.includes(image)}
>
<img src={image} alt="media" />
</div>
))}
</div>
<button onClick={handleAddClick} disabled={selectedImages.length === 0}>
Add {selectedImages.length > 0 ? `(${selectedImages.length})` : ''} Images
</button>
<style jsx>{`
.media-popup {
padding: 20px;
}
.image-grid {
display: grid;
grid-template-columns: repeat(auto-fill, minmax(100px, 1fr));
gap: 10px;
}
.image-item {
cursor: pointer;
border: 2px solid transparent;
transition: border-color 0.3s ease;
}
.image-item img {
max-width: 100px;
height: auto;
}
.image-item.selected {
border-color: blue; /* Border for selected images */
}
button {
margin-top: 20px;
padding: 10px;
background-color: #007bff;
color: white;
border: none;
cursor: pointer;
border-radius: 5px;
}
button:disabled {
background-color: grey;
cursor: not-allowed;
}
`}</style>
</div>
);
🧰 Tools
🪛 GitHub Check: ESLint

[warning] 38-38: Prevent usage of <img> element due to slower LCP and higher bandwidth.
Using <img> could result in slower LCP and higher bandwidth. Consider using <Image /> from next/image to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

@nevo-david nevo-david closed this Feb 6, 2025
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.

6 participants