Supporting files and containers (loopback-component-storage)

[abbasmousavi]

Does javascript support files and containers like iOS and android clients?

[bajtos]

There isn't a first class support in the LoopBack Angular SDK yet, but you should be able to upload files using the angular-file-upload plugin. Checkout the example app in loopback-storage project.

[bajtos]

If we want to implement a generic solution that is not couply tied with loopback-component-storage, then we need to implement support for stream arguments in strong-remoting first - see strongloop/strong-remoting#35.

[bajtos]

Related: https://groups.google.com/forum/#!topic/loopbackjs/sjs_kt07LSw

[reichert621]

The example 2.0 is pretty helpful. I also created a gist of the bare minimum I needed to do to get file upload working with ng-file-upload, because I was struggling for a bit to figure it out: https://gist.github.com/reichert621/e987545fdbc2bc071d37

[TeknoloGenie]

I was looking for an example through google for the example that both @reichert621 and @bajtos provided and couldn't find it, low and behold its been relocation to the production branch, heres the link for future googler's. angular file upload using loopback-component-storage

[z3dmax]

Please add that feature to loopback-sdk-angular!!! I've past a day how to figure out a solution using lbServices in my Ionic App to upload an image using method lbServices.ImageResource#upload until I found out that it's not implemented yet... and now I'm planning to do using $cordovaFileTransfer with multipart-form-data and standard API.... it's gonna work?

[bajtos]

I am afraid we don't have bandwidth to implement this feature ourselves. Contributions are welcome though!

[smehrbrodt]

I am afraid we don't have bandwidth to implement this feature ourselves. Contributions are welcome though!

Then just leave the issue open?

[bajtos]

Then just leave the issue open?

We are trying to clean up our issue trackers to make them easier to work with. Having open issues that nobody is going to work on any time soon is too cumbersome. Since there was no activity in this issue for almost two years, it's pretty safe to assume there is nobody willing to contribute a pull request. We can always re-open if somebody comes with an offer to implement the necessary changes.