-
Notifications
You must be signed in to change notification settings - Fork 97
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
Use ember-ajax as base #118
Comments
I'm all for keeping up with what is current in Ember. |
One thing to be careful of is that any time you create an object with |
@jamesarosen Can you elaborate on that? I have used that pattern previously, and I was unaware of that possibility. What is required to tear down an object like that properly? |
I can! The issue is that the uploader: Ember.computed(function() {
return EmberUploader.Uploader.create(...);
}) since then the component is definitely holding on a reference. The solution is to call |
We have an application that uses Ember-Uploader and Ember-AJAX together. Because Ember-Uploader uses
Ember.$.ajax
directly, it doesn't take advantage of any global settings we've done in Ember-AJAX like headers and error-handling.What do you think of swapping in Ember-AJAX for the transport? Because it's container-based, one change that would be required (or a workaround found) would be
The text was updated successfully, but these errors were encountered: