[ 
https://issues.apache.org/jira/browse/COUCHDB-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14342259#comment-14342259
 ] 

ASF GitHub Bot commented on COUCHDB-2237:
-----------------------------------------

GitHub user robertkowalski opened a pull request:

    https://github.com/apache/couchdb-chttpd/pull/28

    add _changes?feed=stream sugar for continuous

    allow `feed=stream` as sugar for `continuous` which is hard to
    type.
    
    closes COUCHDB-2237

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/robertkowalski/couchdb-chttpd 2237-stream

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/couchdb-chttpd/pull/28.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #28
    
----
commit 53b35d9977c8a3947b6ca51d2826adf0892bfe5c
Author: Robert Kowalski <r...@kowalski.gd>
Date:   2015-03-01T14:42:24Z

    add _changes?feed=stream sugar for continuous
    
    allow `feed=stream` as sugar for `continuous` which is hard to
    type.
    
    closes COUCHDB-2237

----


> Add a 'live' sugar for 'continuous'
> -----------------------------------
>
>                 Key: COUCHDB-2237
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2237
>             Project: CouchDB
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: HTTP Interface
>            Reporter: Dale Harvey
>            Assignee: Robert Kowalski
>
> With PouchDB we generally try to stick to the same param names as Couch, we 
> are even changing some we implemented first to be compatible 
> (https://github.com/pouchdb/pouchdb/issues/2193)
> However 'continuous' sucks to type, its confusing to type and spell and 
> everyone gets it wrong, we still support it but switched to documenting it as 
> 'live' and life is awesome again



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to