Any thoughts on how to deal with this via change detection?
I'm having the same problem - changes to attributes on the file-item do not trigger change detection and thus my templates do not update.
Simplified my code looks like:
``` html
<ul>
<upload-item *ngFor="#item of uploader.queue" [item]="item"></upload-item>
</ul>
```
``` javascript
...
export class UploadItemComponent {
@Input() item
}
```
``` html
<p>Error: {{item.isError}}, Uploading: {{item.isUploading}}, Ready: {{item.isReady}}, Success: {{item.isSuccess}}, Canceled: {{item.isCancel}}</p>
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
See: https://github.com/valor-software/ng2-file-upload/issues/29
Fixed by updating progress inside zone.run()
hey, thanks for PR
direct working with zone.js could be dangerous in long run
any way to fix this with change detection strategies?
Any thoughts on how to deal with this via change detection?
I'm having the same problem - changes to attributes on the file-item do not trigger change detection and thus my templates do not update.
Simplified my code looks like:
Thanks for your help :)