-
Notifications
You must be signed in to change notification settings - Fork 33
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
Unclear how to specify options #91
Comments
@simenheg Absolutely! Labelled as a bug, as options should be persisted. |
Bumping this, as I am running into the options being overridden too. Is there a version that's Ember 2.0 compatible that doesn't override custom options? |
+! |
Anyone forked a working version? |
I've pushed out an emergency release of |
great thanks a lot, will test in the next day or so. |
No. trying to understand your use of
=> $E.options.mimeTypes is still the default one |
easy short term fix is to set directly the option hash on the extending component, using all the keys of
|
@Leooo I can't seem to get your suggestion to work |
I managed to find a solution that works. You can override the initializer and set the options after export default Ember.Component.extend(Droplet, {
init: function() {
this._super.apply(this, arguments);
this.set("options.uploadImmediately", true);
}
}); |
It's unclear how options can be specified when instantiating a component that extends
Droplet
. The documentation says:This suggests to me that options are set directly as properties on the component, like so:
Or even:
However I was surprised to find that these properties are overridden when the component is instantiated. I think this should be clarified in the documentation, or the behavior changed to keep option properties set on the component.
The text was updated successfully, but these errors were encountered: