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(blade): File upload does not fire change input event when file is dropped [DSSUP-128] #2402

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

tewarig
Copy link

@tewarig tewarig commented Nov 4, 2024

Description

FileUpload component does not fire change or input event when the file is dropped.

Changes

  • Add onInput as prop in FileUpload
  • now, file Input fires onChange , onInput when a file is dropped.

Additional Information

Component Checklist

  • Update Component Status Page
  • Perform Manual Testing in Other Browsers
  • Add KitchenSink Story
  • Add Interaction Tests (if applicable)
  • Add changeset

Copy link

changeset-bot bot commented Nov 4, 2024

🦋 Changeset detected

Latest commit: c257e6d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@razorpay/blade Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link
Contributor

github-actions bot commented Nov 4, 2024

✅ PR title follows Conventional Commits specification.

@tewarig tewarig changed the title Fix(blade) : File upload does not fire change input when file is dropped fix(blade) : File upload does not fire change input when file is dropped Nov 4, 2024
@tewarig tewarig changed the title fix(blade) : File upload does not fire change input when file is dropped fix(blade): File upload does not fire change input when file is dropped Nov 4, 2024
Copy link

codesandbox-ci bot commented Nov 4, 2024

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit c257e6d:

Sandbox Source
razorpay/blade: basic Configuration

@tewarig tewarig changed the title fix(blade): File upload does not fire change input when file is dropped fix(blade): File upload does not fire change input event when file is dropped Nov 4, 2024
@rzpcibot
Copy link
Collaborator

rzpcibot commented Nov 4, 2024

Bundle Size Report

Updated Components
Status Component Base Size (kb) Current Size (kb) Diff
FileUpload 17.119 17.164 +0.045 KB
Link 2.115 2.114 -0.001 KB

Generated by 🚫 dangerJS against c257e6d

/**
* Callback function triggered when files are selected or when a file is dropped into the upload area
*/
onInput?: ({ name, fileList }: { name?: string; fileList: BladeFileList }) => void;
Copy link
Member

Choose a reason for hiding this comment

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

This seems same as onChange , are we planning to deprecate the onChange prop in favor of onInput? If so, we need to update the description accordingly.

Copy link
Author

@tewarig tewarig Nov 4, 2024

Choose a reason for hiding this comment

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

In the case of FileUpload, both onChange and onInput should exhibit the same behavior.
CodePen example demonstrates this.

Currently, however, the FileUpload component lacks an onInput prop, so it does not trigger the onInput event when a file is dropped. we need to ensure that native input events are triggered in FileUpload for Analytics SDK .
https://razorpay.atlassian.net/browse/DSSUP-128

@tewarig tewarig changed the title fix(blade): File upload does not fire change input event when file is dropped fix(blade): File upload does not fire change input event when file is dropped [DSSUP-128] Nov 5, 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.

3 participants