-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Access to nano or database handler #6
Comments
Sorry, I took c.stool.driver() out following the major refactoring few versions ago, thinking that no one uses it. The above commit added it back, you should be able to get a handle of the driver using util.driver (object, not function) from the tasks. Would this cover what you need? |
I think it would and I'm updating the code to use the new util.driver (not util.driver()) mechanism At the moment, util.driver is undefined inside my task though... |
Ah, seems that I'm still on 0.1.1, so probably don't have your commit yet... |
I just published v0.1.2, please npm install -g couchtato, then couchtato --version to confirm that you get 0.1.2 . From the task function, you can use util.driver directly, there's no need for 'new'.
Inspect util.driver to see what nano#use provides. Please let me know if it works for you. |
Looks good! Thanks very much! |
Cool. Thanks for reporting this in the first place :). |
Is there any way to get access to nano from within a task to do other work/verification? In the previous version, one could call c.stool.driver() from a task to get access to cradle, but since the arguments are now util and doc, there doesn't seem to be an easy way to get the database handle...
The text was updated successfully, but these errors were encountered: