This repository has been archived by the owner on Nov 5, 2018. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the ability to get at the
serverScope
from adocScope
. (which is not currently possible)If you initialize nano with a db-name in your URL, (a common practice) it effectively becomes impossible to access the server scope:
In my case, I'm using a single database for my application, but I'm also trying to use
_users
for handling auth. I'm forced to create 2 different nano refs, which is just a little clumsy.This PR adds support for the following:
While I could just say this is a convenience method, I think it's a little bit more than that since a common pattern like specifying a db-name completely excludes this functionality.