Applications using this SDK must run inside an iframe of the Home, otherwise they won't get the token.
When we are unable to get the auth token, we should display a warning, explaining the user the application cannot be used alone.

We intensively Backbone in Cozy apps, and the CRUD actions from Backbone.Model with cozy sync is generally the same each times (see https://github.com/cozy-labs/cozy-music/pull/3/files#diff-0b06487a4bbf3713e0cfac841fc4f92cR23). We can provide a module with a Backbone.sync wrapper to CozySDK that can be quickly embed to our apps to plug our models with the CozySDK directly.

Currently we must wait until each request has been created to launch the app.

On most of our own applications, we have a method that allow to log client-side errors into application logs. It would be nice to provide such a method to serverless applications.
Once done, this method could be used inside our own applications, instead of current duplicated code.

/cc @m4dz

When running a request (run, create, destroy…) it may sometimes be useful to get a Promise rather than deal with callbacks. I think we can easily support both, and then let the playRequest helper returns a Promise too.

@aenario, sounds good to you?

When perfoming a request, the documentation recommand to do a items = JSON.parse('' + res) to get the JSONified result. As long as the expected result is always a JSON object, this post-treatment should be done by the SDK, not the app itself.

We need to find a proper API, I offer :

Option 1 - mikeal/request like, where we return the xhr object, so the app can setup its listeners

file = document.getElementbyId('input_file').files[0]
request = cozysdk.attachBinary 'Note', 454id543, 'binary_name.ext', file, callback
request.addEventListener("abort", transferCanceled);
request.upload.addEventListener("progress", updateProgress);
request.upload.addEventListener("abort", transferCanceled);

Option 2 - with a progressback

file = document.getElementbyId('input_file').files[0]
progressback = (event) -> event instanceof ProgressEvent
cozysdk.attachBinary 'Note', 454id543, 'binary_name.ext', file, callback, progressback

*1 event is a ProgressEvent

Option 3 - only provide the url, and some doc on how to use it with <form>

Ideally, we should blur the line and use the same API. (can be done DS side)

 cozysdk.create('Track', model, (error, response) => {
    console.log('CREATE TRACK', error, response);
});

when an object is created the response looks like this :

CREATE TRACK null Object { _id: "6ff5933b1feaf95ed8068bd78303431d" }

it would perhaps be better if we would have the full document created (with all attributes)

Hi,

I am quite new to CouchDB, so I might miss something, but how are multiple defineView handled? I have two main concerns:

1. First one is that if I defineView a previously defined view, it will overwrite it. Is there any plans (maybe in the long term) to ensure a Cozy app cannot override pre-existing views and potentially break other installed apps?
2. When multiple apps get installed, all of them will populate the views by defining their own. But nothing seems to clean the defined views, for example when apps are uninstalled. Then, the number of views in the CouchDB can only keep increasing. Is there any mechanism to clean the useless views or is it of no importance?

Thanks!

Options :

• Rename functions to use the "view" word instead of "request", improve doc and point to couchdb doc.
• Use pouchdb-find to generate map & reduce functions

http://cozy.github.io/cozy-browser-sdk/module-mapreduce.html#.defineMapReduceView
https://github.com/cozy/cozy-browser-sdk/blob/master/src/index.coffee#L17

When creating a document with sdk-client the docType key is not set.

hi,
after a npm i cozysdk-client -- save ("cozysdk-client": "0.0.5")
i use CommonJS and so i need to do into app.js
var cozysdk = require('../vendor/cozysdk-client');

an npm build return this error:
Error: Cannot find module './utils/client' from '/myproject/vendor'
Error: Cannot find module './utils/client' from '/stuff/myproject/node_modules/cozysdk-client/dist'

ls /node_modules/cozysdk/

• dist

ls /node_modules/cozysdk-client/dist

• cozysdk-client.js
• cozysdk-client.js.map

with the https://cdn.rawgit.com/cozy/cozy-browser-sdk/wip-v1/dist/cozysdk-client.js
everything was fine
https://github.com/cozy/cozy-browser-sdk/blob/master/dist/cozysdk-client.js#L5

So maybe it miss the ./utils folder into the npm version?

Test this part of the code to see if it works in both http and https pages and if we should remove the encodeURI.