This repository was archived by the owner on Jun 5, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 149
Eliminate invalid callbacks to onChange prop #51
Comments
Facing the same issue. |
@donalmurtagh Do you know when fix will be released? |
@vovkind I don't have permission to do releases, you'll have to ask @JakeHartnell. While you're waiting for a release, you can copy
from my PR branch into your project and use those instead of the files in |
Guys, I'm still facing the issue with v1.2.0 My code is the same code as in the example. Can you please check again? |
@vovkind check what? If you have a problem, please open an issue with an example that reproduces it. |
@vovkind could you create a Plunker/JSFiddle (or similar) demo that reproduces the issue with version 1.2.0? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In this example usage, I upload 2 files, one of which is 2.7MB and the other is 4.2MB. Notice that the
onChange
prop is called back multiple times. The first time it is called back, only the first uploaded file is provided in the arguments, the second time it is called back, both files are provided in the arguments, etc.You can see evidence of this in the console output of the example above
Similarly, if 3 files are uploaded,
onChange
is called back 3 times with 1, 2, and 3 files respectively.We should instead callback to
onChange
only once, providing all successfully processed files in the arguments.I'm pretty sure that this bug was introduced recently, probably during the last month or two. The performance on the demo website is much better. My guess is that the demo site is using an older version of the component that does not include this bug.
The text was updated successfully, but these errors were encountered: