couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robertkowalski <>
Subject [GitHub] couchdb pull request: COUCHDB-2125 Sort tasks
Date Tue, 08 Apr 2014 19:48:54 GMT
GitHub user robertkowalski opened a pull request:

    COUCHDB-2125 Sort tasks

    This might need some styling / concept love and I hope I understood the comments in the
    This PR includes a heavy refactor, which is also a separate PR #203 which can get merged
earlier without a discussion regarding the concept and design, and I will update this PR as
the other PR changes.

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

    $ git pull 2125-sort-tasks-feature

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

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

    This closes #204
commit 75f9a04e116fcee353e1d81dd61ff69867d868f5
Author: Robert Kowalski <>
Date:   2014-04-06T16:17:36Z

    Fauxton: reformat code & remove whitespace

commit 887f004ffbbb1ff04d2e7f686f17b0068228367c
Author: Robert Kowalski <>
Date:   2014-04-06T21:15:16Z

    Fauxton: refactor ActiveTasks
    - do not use a model as a collection, directly operate on the
      collection which gets filtered for the view
    - remove the view which acted as layer to fetch collections from
      the model and passed it to a view
    - remove not used html-template
    - format code

commit 7090bd51863f9be2bb588a399274a534946dff1a
Author: Robert Kowalski <>
Date:   2014-04-06T21:42:04Z

    Fauxton: do not load unnessecary d3 & backbone

commit b8dc9958108dadfa9e81596333117e4424f6648a
Author: Robert Kowalski <>
Date:   2014-04-08T19:26:47Z

    Fauxton: Add sorting buttons
    Fixes COUCHDB-2125


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message