RFC: Angular wrapper about filepond

[rikschennink]

@vitaliy-bobrov I'd love to!

1. FilePond was originally going to be a commercial plugin, but has since moved to MIT, that's the reason why only the build targets are available. I'm planning to add the source files in the near future, but want to clean them up and streamline the build script first.

2. You can set up custom file processing methods which allow you to completely customize uploads (and other requests).

3. I'm not sure what you mean with DOM manipulations, please elaborate.

[vitaliy-bobrov]

Under DOM manipulations I mean add/remove DOM nodes, etc. But we can wrap filepond calls inside separate zone with NgZone API to avoid unnecessary change detection calls.

[rikschennink]

There's no manipulation of the DOM outside of the FilePond root node. You can create a pond without having a target element to bind to (it will then create a node itself), the element will be available in from the element property. You can then add that element to the page manually.

I have limited experience with Angular 1, 2 and up. But if NgZone blocks mutation events than if the Angular component wraps the FilePond element in one of those, all should be fine.

Maybe the React Component can function as a reference.

[vitaliy-bobrov]

Thanks for the explanation, I need to investigate how it works and will experiment on Angular wrapper.

[rikschennink]

No problem, let me know if you've got any questions, happy to help 👍

[rikschennink]

@vitaliy-bobrov I've set up an adapter for Angular here, I'm no pro at this, but it seems to work, probably lots of room for improvement.