-
Notifications
You must be signed in to change notification settings - Fork 350
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
7 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
5d171ad
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, I see you restored the change on #128 which was merged to master with this commit #129. And now I see again the bug #87.
Could you explain us if #87 is a real bug? And if that so, tell us why you restored that change so maybe I can work on other fix.
5d171ad
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Its not a real bug. This means that module is not properly included. Please check your console for errors.
5d171ad
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I guess you are not having this issue:
I don't undesrtand why the issue may be related with the way I'm using modules cause I'm using them with other modules, components, services and they are correctly called from other places.
For Ng2UploaderModule I'm using this on a sharedModule
And then on the components I want to use it I import the shared module
If I change the Input() decorator above the options property definded with the get then I no longer see the issue with the binding.
5d171ad
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you check your network tab if
ng2-uploader.js
gets loaded?5d171ad
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see ng2-uploader.js on network-tab.. neither if I change the input() decorator above the getter (in which case the issue with the options binding disapear). I'm still new on angular, didn't make any build yet.
I also found this other issue related on how to declare a property binding.
http://stackoverflow.com/questions/36653678/angular2-input-to-a-property-with-get-set. That guy has the exact same issue we are seeing with the [options] binding and on the plunker they provide the issue is solved by setting the Input() decorator above the getter.
5d171ad
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you have this a project or starter which you can share (append)
.zip
here? I have time right now and I can take a look.5d171ad
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I can't. But I have the plunker modified where you can check the Input() decorator doesn't work above the setter.
https://plnkr.co/edit/LgVtWlSZjrXRMWvJvCIe?p=preview
This is my package.json
5d171ad
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, it looks this was an old bug on angular I guess angular/angular#5477.
So it looks the workaround is to declare the Input() decorator at first... (no matter if it's on the getter or setter)
But I don't understand why it's working with some people and not for others. Defenitely it's not a bug from ng-upload module. I'd like to know which configuration we are missing.