GitHub user robertkowalski opened a pull request:

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

    Revert "JS validation added for Add Database"

    This reverts commit b8bbb87c6919469521ff277694fb75e898157a7c.
    
    The commit was added in https://github.com/apache/couchdb-fauxton/pull/468
    but the validation has to happen in the backend. The current
    validation does not cover databases which are created via curl or
    other apps. It also prevents users from creating an accidentally
    deleted `_users` database.
    
    The fix for the root cause has to happen in the backend.
    
    We should avoid trying to add validations in multiple, different
    places.
    
    COUCHDB-2748

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

    $ git pull https://github.com/robertkowalski/couchdb-fauxton 
2748-ids-validation-users-db

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

    https://github.com/apache/couchdb-fauxton/pull/662.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 #662
    
----
commit c8d959591bbca1f718ea2335a95cdfb5bf0bdaec
Author: Robert Kowalski <[email protected]>
Date:   2016-03-08T19:12:04Z

    Revert "JS validation added for Add Database"
    
    This reverts commit b8bbb87c6919469521ff277694fb75e898157a7c.
    
    The commit was added in https://github.com/apache/couchdb-fauxton/pull/468
    but the validation has to happen in the backend. The current
    validation does not cover databases which are created via curl or
    other apps. It also prevents users from creating an accidentally
    deleted `_users` database.
    
    The fix for the root cause has to happen in the backend.
    
    We should avoid trying to add validations in multiple, different
    places.
    
    COUCHDB-2748

----


---
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.
---

Reply via email to