-
Notifications
You must be signed in to change notification settings - Fork 157
Conversation
Sorry I'm confused, why is this more than just updating the following dependency? I don't see any deleted code. Thanks for the code, looking forward to understanding this a bit better |
Sorry if my explenation was not clear - I have added |
Ok. If that's the case please de-duplicate the code and make sure they use the same helper function, but with the different URL. I'm ok with the API change but duplicated code makes it complicated (as noted by my remarks) Thanks 💯 |
Also 📖 docs ! |
Oh f* I forgot the docs. |
Here again, squashed, with docs. |
Looks good. Are you sure you want to name it Other than that, good to merge |
We have |
What about |
Lets call it |
Did the name change in code, commit msg as well as in issue and PR descriptions. |
... and fixed the tests for |
`nano.follow_updates([params], [callback])` uses follow to create a solid `_db_updates` feed. please consult follow documentation for more information as this is a very complete api on it's own ```js var feed = nano.follow_updates({since: "now"}); feed.on('change', function (change) { console.log("change: ", change); }); feed.follow(); process.nextTick(function () { nano.db.create('alice'); }); ```
merged :) publish? |
Thanks and yes please publish ;-) |
done :) |
nano.follow_updates([params], [callback])
uses follow to create a solid
_db_updates
feed. please consult followdocumentation for more information as this is a very complete api on it's own