Permalink
Commits on Jan 11, 2014
  1. Merge pull request #172 from jo/multipart

    dscape committed Jan 11, 2014
    (#171) - multipart api
  2. (#171) - multipart api

    jo committed Jan 11, 2014
    Introduce `db.multipart` api endpoint for making multipart/related requests:
    
        db.multipart.get(doc, attachments, [params], [callback])
        db.multipart.insert(doc, attachments, [params], [callback])
    
    Note: the `db.multipart.get` response is an unparsed `Buffer`.
Commits on Dec 5, 2013
  1. Update nano.js

    juehuizh authored and mmalecki committed Dec 4, 2013
Commits on Nov 19, 2013
  1. Update README.md

    dscape committed Nov 19, 2013
Commits on Nov 15, 2013
  1. laxcomma

    dscape committed Nov 15, 2013
  2. [regression] Re-introduces request_defaults

    dscape committed Nov 15, 2013
    * Fixes #162
    * Adds @buildmaster to the contributors
    * JSHint was not happy with `nano`, minor fixes
Commits on Nov 11, 2013
  1. [4.2.0] Default Header Support

    dscape committed Nov 11, 2013
    * Fixes problem with specify not showing syntax errors
    * Adds `cfg.default_headers`
    * Allow for providing a custom `request` option
    * Fix a revision problem
    * Runs unmocked tests in CI system
  2. Fixes #158

    dscape committed Nov 11, 2013
  3. Adds mocks for default headers

    dscape committed Nov 11, 2013
  4. Merge pull request #161 from jkrems/jk/global_default_headers

    dscape committed Nov 11, 2013
    Allow for global default headers
  5. Merge pull request #159 from mmalecki/request

    dscape committed Nov 11, 2013
    [api] Allow for providing a custom `request` option
Commits on Nov 10, 2013
Commits on Oct 29, 2013
  1. Fix a revision problem

    Gerrit Renker authored and mmalecki committed Oct 29, 2013
  2. Fix a document update conflict in tests

    Gerrit Renker authored and mmalecki committed Oct 29, 2013
Commits on Oct 28, 2013
  1. [api] Allow for providing a custom `request` option

    mmalecki committed Oct 28, 2013
    Since monkey punching `nano` is impossible, allow user to provide a
    custom `request` option for failovers and similar.
Commits on Oct 8, 2013
  1. dist 4.1.4

    dscape committed Oct 8, 2013
  2. Merge pull request #153 from alappe/att_name_missing

    dscape committed Oct 8, 2013
    throw error if att_name is missing in destroy call
Commits on Sep 24, 2013
  1. Merge pull request #155 from aramkocharyan/master

    dscape committed Sep 24, 2013
    Fixed typo - I think 'rabbit' is used consistently as the doc in the 'alice' db.
Commits on Sep 15, 2013
  1. throw error if att_name is missing in destroy call

    alappe committed Sep 15, 2013
    As the att_name is used in constructing the url to send the DELETE call
    to, using something like false or an empty string results in deleting
    the whole document. This should not happen…
Commits on Sep 6, 2013
  1. 4.1.3

    dscape committed Sep 6, 2013
    Updates dependencies
    Fixes bug with views with empty params
  2. 4.1.3

    dscape committed Sep 6, 2013
    Updates dependencies
    Fixes bug with views with empty params
  3. 4.1.2

    dscape committed Sep 6, 2013
  4. views: make params parameter for view_docs{,_with_list} optional

    Gerrit Renker authored and dscape committed Sep 6, 2013
    The documentation says that `params` argument of the db.view() and db.view_with_list()
    functions is optional. If omitting the parameter instead of passing an empty object, it
    complains about a "TypeError: Cannot read property `keys` of undefined".
    
    With this change, it is possible to omit the `params` argument without the exception.
    
    Signed-off-by: Nuno Job <nunojobpinto@gmail.com>
Commits on Aug 22, 2013
  1. Merge pull request #152 from garbados/typo

    dscape committed Aug 22, 2013
    Typo
  2. fixed typo

    garbados committed Aug 22, 2013
Commits on Jul 19, 2013
  1. New release in the oven

    dscape committed Jul 19, 2013
  2. db.follow: escape URL

    dscape committed Jul 19, 2013
    A db_name may contain slashes, but these need to be escaped as %2F in URLs.
    The other parts of the nano API deal with this, only with the follow API
    I ran into this issue, since we use a hierarchical structure like
    
      rbuilder/client_A/agreements/agreement_1
      rbuilder/client_A/agreements/agreement_2
      rbuilder/client_B/agreements/agreement_1
    
    by email by Gerrit Renker