[GitHub] couchdb-fauxton issue #761: New replication

[justin-mcdavid-ibm <gi...@git.apache.org>]

Github user justin-mcdavid-ibm commented on the issue:

    https://github.com/apache/couchdb-fauxton/pull/761
  
    With regard to trying to start a replication job that uses a custom doc ID that conflicts with that of an existing document, we should be providing validation of some sort, and then giving the user a choice on what action to take.
    
    Currently, if I fill out details for a remote replication job, but make a small mistake on the url/password, the replication document will be created, but the replication job will fail.  If I want to go in an make a small tweak to fix the details, but use the same custom ID, I'll get a doc-conflict error warning, and will then either need to manually delete the first document or change the custom doc ID to something new (at which point I'd probably want to delete the doc for the failed job just to keep things tidy).
    
    My recommendation is to provide a validation step in between clicking the "Start Replication" button and the replication document actually being created/sent to the server.  If validation fails, give the user an opportunity to delete the existing, conflicting replication document before creating the new one.
    <img width="428" alt="artboard 1 copy 4" src="https://cloud.githubusercontent.com/assets/12969375/18851240/d6f9644c-83ef-11e6-9979-051e99db557f.png">



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