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

fix: add multiple prop to dropzone #1487

Closed
wants to merge 1 commit into from
Closed

Conversation

okosohor
Copy link

@okosohor okosohor commented Nov 15, 2024

Closes #

πŸ“‘ Description

Add multiple prop to Dropzone, because now we have possibility to load many files only with drag & drop

Status

  • Not Completed
  • Completed

βœ… Checks

  • My pull request adheres to the code style of this project
  • My code requires changes to the documentation
  • I have updated the documentation as required
  • I have checked the page with https://validator.unl.edu/
  • All the tests have passed
  • My pull request is based on the latest commit (not the npm version).

β„Ή Additional Information

Summary by CodeRabbit

  • New Features
    • Introduced an optional property to the Dropzone component, enabling support for multiple file uploads.
    • Enhanced file input functionality to allow users to select multiple files when desired.

Copy link

vercel bot commented Nov 15, 2024

@okosohor is attempting to deploy a commit to the Themesberg Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

coderabbitai bot commented Nov 15, 2024

Walkthrough

The changes introduce a new optional property multiple to the DropzoneProps interface in the Dropzone.svelte file, enabling the component to accept multiple file uploads. The multiple property defaults to false and is bound to the input element, allowing users to select multiple files when enabled. The overall functionality and structure of the component remain unchanged aside from this enhancement.

Changes

File Change Summary
src/lib/forms/Dropzone.svelte Added multiple property to DropzoneProps interface, initialized to false, and updated input element to bind the multiple attribute.

Possibly related PRs

Poem

In the meadow where bunnies play,
A new way to upload files today!
With a hop and a skip, we can choose,
Multiple files, oh what a muse!
Dropzone's magic, so easy and bright,
Bouncing with joy, we share our delight! πŸ‡βœ¨


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 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.

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: 0

🧹 Outside diff range and nitpick comments (1)
src/lib/forms/Dropzone.svelte (1)

Line range hint 1-48: Consider enhancing the drag and drop experience

While the multiple file support is implemented correctly, the user experience could be improved.

Consider these enhancements:

  1. Update the drag-and-drop visual feedback to indicate multiple file support
  2. Add a prop to limit the number of files that can be selected
  3. Add validation for allowed file types when multiple files are selected

Would you like me to provide implementation suggestions for any of these improvements?

πŸ“œ Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 6542fdb and 0cc1052.

πŸ“’ Files selected for processing (1)
  • src/lib/forms/Dropzone.svelte (3 hunks)
πŸ”‡ Additional comments (4)
src/lib/forms/Dropzone.svelte (4)

9-9: LGTM! Clean interface extension

The multiple property is correctly added as an optional boolean to the DropzoneProps interface.


17-17: LGTM! Property export follows conventions

The multiple property export is well-typed and has a sensible default value of false.


38-38: Verify accessibility for multiple file selection

The input binding looks correct, but we should ensure proper accessibility for multiple file selection scenarios.

Consider adding an ARIA label that indicates multiple file selection is possible when multiple is true:

-  <input {...$$restProps} {multiple} bind:value bind:files bind:this={input} on:change on:click type="file" />
+  <input 
+    {...$$restProps} 
+    {multiple} 
+    bind:value 
+    bind:files 
+    bind:this={input}
+    aria-label={multiple ? "Choose files" : "Choose a file"}
+    on:change 
+    on:click 
+    type="file" 
+  />

48-48: LGTM! Documentation is up to date

The new property is properly documented following the existing format.

Copy link

vercel bot commented Nov 15, 2024

The latest updates on your projects. Learn more about Vercel for Git β†—οΈŽ

Name Status Preview Comments Updated (UTC)
flowbite-svelte βœ… Ready (Inspect) Visit Preview πŸ’¬ Add feedback Nov 15, 2024 4:16pm

@shinokada
Copy link
Collaborator

Since the component is extended HTMLInputAttributes, and {...$$restProps} is in the input tag, you don't need it.
See https://github.com/sveltejs/svelte/blob/svelte%405.1.9/packages/svelte/elements.d.ts#L1049

@shinokada shinokada closed this Nov 16, 2024
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.

2 participants