GitHub user robertkowalski opened a pull request:
https://github.com/apache/couchdb-fauxton/pull/437
Fix accepted
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/robertkowalski/couchdb-fauxton fix-accepted
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/couchdb-fauxton/pull/437.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 #437
----
commit 455f0a53b068b6e6fdbd17c6f050852cc60bad3b
Author: Robert Kowalski <[email protected]>
Date: 2015-05-19T17:57:38Z
tests: don't delete _replicator every time
- we just need the replicator db for one test, so do the cleanup
just there. saves one request for all other tests
- try to fix flaky tests
- cleanup mocha tests
- make react 13 compatible
- do not patch jquery
- fix async race conditions
- do not couple tightly to implementation (event handlers)
- a dedicated db for create databases
- tests: createBadView - harden test
- viewEdit.js fix
- paginateAllDocs.js tweak
- viewCreateBadView: work on selectors
- delete meaningless test
the div #globalnotifications exists always
- .click -> clickWhenVisible
- verifyInstallTest
- add helpers, do not rely on notifications
- add spy.restore()
- make sure changes are there opening the page & before asserting
PR: #423
PR-URL: https://github.com/apache/couchdb-fauxton/pull/423
Reviewed-By: Benjamin Keen <[email protected]>
commit f93372389e1780cd8d9e9baf00cab86783673cb8
Author: Garren Smith <[email protected]>
Date: 2015-04-27T12:29:54Z
Fauxton Server for use with NPM
This allows Fauxton to be installed via npm so that we can release newer
versions of Fauxton for users to try out.
$ npm install fauxton -g
$ fauxton
or see `fauxton --help` for options
commit 63e130b4217c1ad51d1a22395c5ee0c448bf69bd
Author: Robert Kowalski <[email protected]>
Date: 2015-05-26T12:04:20Z
devserver: fix exception if no accept-header set
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
