nano options lost in DB scope

[tlvince]

If you pass in a nano config as the url, e.g. to set requestDefaults (#14):

bootstrap({
  url: 'http://localhost:5984',
  requestDefaults: {
    auth: {
      user: 'admin',
      pass: 'admin'
    }
  }
}, 'path/to/fs', cb)

… requestDefaults is lost after nano.use, for example in secure:

// ...
var dbname = utils.mapDbName(filename, options)
var db = couch.use(dbname)
console.log('couch: ', couch.config, '\ndb: ', db.config)
// =>
// couch:  { url: 'http://localhost:5984',
//  requestDefaults: { jar: false, auth: { user: 'admin', pass: 'admin' } },
//  defaultHeaders: { 'X-Couch-Full-Commit': 'true' } } 
// db:  { url: 'http://localhost:5984', db: '_users' }

In this case, this will cause subsequent requests to 401 (You are not authorized to access this db.).

Perhaps this is an issue with nano itself (https://github.com/dscape/nano/issues/278)?

[jo]

This is an interesting issue. Will investigate. This might be a bug in nano, but https://github.com/dscape/nano/issues/278 is a different one.

[jo]

Seems like this is not nanos problem

[jo]

db.config does not get the initial config but is only a stub with url and db, see here: https://github.com/dscape/nano/blob/master/lib/nano.js#L693

Nonetheless the config should be used like tested here: https://github.com/dscape/nano/issues/296

[tlvince]

Sorry, so was this an issue with the way I was calling it or something in nano-option?