mikepb / clerk Goto Github PK

To seamlessly support co, return Promises if no callback is provided.

Superagent supports both node and the browser. We unify the node and browser network implementations with superagent while also taking experimental browser support out of experimental status.

https://github.com/visionmedia/superagent

COPY in CouchDB 1.2 updates the revision whereas CouchDB 1.1.1 does not.

Ref: COUCHDB-1485

The source documentation has links to the old CouchDB wiki. We should update these links.

If you'd like to help, please let me know!

I created clerk around the same time as the nano CouchDB client project started, but didn't market the project at all. Now, nano forms the basis of the Cloudant library and there's talk about adopting nano as the official CouchDB client for JS.

Needless to say, I'm biased towards preferring the clerk API over nano. I think that creating a nice page for promoting and documenting clerk would improve usability and adoption.

If you'd like to help, please let me know!

P.S. Clerk got picked up on the CouchDB Blog 😃
http://blog.couchdb.org/2015/02/03/couchdb-weekly-news-february-03-2015/

Numerous tests fail with a database that requires authentication. I'm not sure if CouchDB likes the xhr auth. I had success converting the auth info into in a Basic Auth header instead of using the xhr user and pass.

The node version of the library uses follow to implement reliable feed subscription. I would like to remove this dependency to allow clerk to be fully supported across node and the browser.

The follow feed listener is designed at a higher level of abstraction than the clerk library. It may be better to create an extension library to keep the core library tight.

• Determine the minimum necessary functionality for reliable subscriptions to the updates feed.
• Design an API suitable for clerk or as an extension.
• Code and test the stuff.

Hey,

Just for completeness I figured I'd post an issue to ask you to set "node": "0.4.x || 0.6.x" in your package.json so we can enjoy this fine-looking module through npm.

It already passes all the tests with Node 0.6.3.

Maybe it's only when I was mucking about with a design document, but the HEAD-request didn't give an error so it failed on this line trying to JSON.parse undefined.

I 'fixed it' by changing that particular line to this:

        rev: JSON.parse(headers.etag||'""'),

I should probably fork and give you pull requests. But this was so tiny, so...next time! :)