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

Handling multiple uppy instances #162

Closed
ctrlplusb opened this issue Feb 22, 2017 · 2 comments
Closed

Handling multiple uppy instances #162

ctrlplusb opened this issue Feb 22, 2017 · 2 comments

Comments

@ctrlplusb
Copy link

I am wrapping uppy in a React Component. The component itself allows you to declare the features you would like to use. I therefore initialize a new uppy instance within each component instance.

Would this be an issue? i.e Is there expected to be only 1 global uppy instance?

Is there any sort of teardown / disposal method I should be aware of.

@arturi
Copy link
Contributor

arturi commented Feb 25, 2017

Hi! Thanks for your interest. I’m currently trying to do the same — wrap Uppy in a React component, that can be easily embedded in an app. Uppy should work fine with multiple separate instances, there is no built-in teardown method. Please let me know how this works out for you and share your code, we might adopt it. Or send as a PR.

goto-bus-stop added a commit to goto-bus-stop/transloadit-uppy that referenced this issue May 2, 2017
@arturi
Copy link
Contributor

arturi commented May 4, 2017

Ok, so thanks to @goto-bus-stop there is now uppy.close(), please let us know if that works for you 👌

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

No branches or pull requests

2 participants