couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From benkeen <...@git.apache.org>
Subject [GitHub] couchdb-fauxton pull request: Fix for lookahead tray redirect prob...
Date Wed, 17 Dec 2014 21:05:12 GMT
GitHub user benkeen opened a pull request:

    https://github.com/apache/couchdb-fauxton/pull/206

    Fix for lookahead tray redirect problem

    This fixes the following problem. To reproduce:
    1. On the All Docs page of a database, edit a document.
    2. Click Back.
    3. Use the lookahead tray to select a new database.
    
    Result: the page was missing content. What was going on was that the
    route object ended up listening to the event multiple times, causing
    the error. This now explicitly cleans up and re-assigns the listeners
    for this scenario.
    
    Closes COUCHDB-2503

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

    $ git pull https://github.com/benkeen/couchdb-fauxton 2503-missing-page-content

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

    https://github.com/apache/couchdb-fauxton/pull/206.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 #206
    
----
commit 62a897f7d7142471da49c51ec75091acd42ac6b9
Author: Benjamin Keen <ben.keen@gmail.com>
Date:   2014-12-17T21:03:46Z

    Fix for lookahead tray redirect problem
    
    This fixes the following problem. To reproduce:
    1. On the All Docs page of a database, edit a document.
    2. Click Back.
    3. Use the lookahead tray to select a new database.
    
    Result: the page was missing content. What was going on was that the
    route object ended up listening to the event multiple times, causing
    the error. This now explicitly cleans up and re-assigns the listeners
    for this scenario.
    
    Closes COUCHDB-2503

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message