first attempt at carbon-pouchdb-auth

[e111077]

General usage:

<carbon-pouchdb-auth db-name="http://remote.address.here:1234/"></carbon-pouchdb-auth>
<!-- ... -->
<script>
auth.login('asdf', 'asdf').then(...).catch(...);

auth.changePassword('new password here').then(...).catch(...);
// for admins
auth.changePassword('new password here', 'otherUser').then(...).catch(...);

auth.updateMetadata({first: 'Ben', last: 'Bitdiddle', email:'bbitdiddle@mit.edu'})
    .then(...).catch(...);
// for admins
auth.updateMetadata({first: 'Ben', last: 'Bitdiddle', email:'bbitdiddle@mit.edu'},
    'bbitsUsername').then(...).catch(...);
// ...
auth.logout().then(...).catch(...);
// success response will be {ok:true, online:{true | false}}
</script>

.session and .isLoggedIn are both read-only. Tests have not been added in yet.

If offline, logout will not delete session cookie, but this element's session object will reflect a logged-out session. (UI logout only)

[cdata]

👍

[cdata]

This is looking great. I kind of want us to add a test, but I'm not sure there is a good way to do that without coming up with a creative way to stub a CouchDB server. So... let's merge it and move on with our lives :)

[e111077]

@cdata changed from carbon -> app, added documentation, and added an isSetup flag. Here is the relevant, readable diff.

[cdata]

There may be many remote databases; the -> a

[e111077]

👍

[cdata]

At what point in the example implementation should the app attempt to log the user in?

[e111077]

I guess you can put it in the authReadyChanged function, but I don't see any practical reason to statically log into a user.

[e111077]

@cdata That little deadlock fix seems to have RESOLVED everything. Get it? Resolve? Promises?

Fine then, don't laugh.

[e111077]

@rictic since Chris is out, do you mind taking a look at this PR?