How to differentiate between multiple UploadDropZone?

[ardian-c]

Hi all,

Thank you for this great library. I'm facing an issue or at least I don't see how to add multiple UploadDropZone components inside Uploady context.
Currently, I have these two dropzones, one for a logo upload and the other one for document upload (csv).
I have useBatchFinishListener for each component, LogoUpload and DocumentUpload.
So, when I upload something say a logo, the listener will show it in both places, which is probably expected behavior for that file listener.
However, I'm struggling to see how should I differentiate between these dropzones, and how should I use the UploadDropZone and listen for the right files in the respective components.
Appreciate any guidance.

[yoavniran]

thanks @ardian-c
This question came up before so I created an example sandbox that helped (for that use case) - Its based on the UploadButton but should apply just the same.

Let me know if it helps you or not.

[yoavniran]

Hey @ardian-c
thats strange
It will be really useful if you can put your example in a reproducing sandbox so I can take a look

[ardian-c]

@yoavniran Here is a sample sandbox

[yoavniran]

works like a charm :)

2022-12-16_16-45-12.mp4

Whats throwing you off most likely is that the upload button isnt sending the param. Thats because you're only passing the uploadType param to the UploadDropZone.

You need to pass the same params to your custom button (calling showFileUpload).

[ardian-c]

@yoavniran Great, I was definitively missing that, I did upload using only the button and that was the confusion. Thank you for your help, appreciated!

One more thing, is it preferred to have a separate Uploady context for these components, or can they be within one context using the current solution to differentiate between them? Are there any drawbacks to these approaches?

[yoavniran]

From my experience using a single context is easier to manage and requires less duplication of code and also less memory footprint (though thats not a major concern typically).

I dont think there's a real drawback to using multiple contexts if that makes sense for your app and the way you structure it.