[GitHub] couchdb-fauxton issue #864: Update replication to work with scheduler api

[justin-mcdavid-ibm]

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

    https://github.com/apache/couchdb-fauxton/pull/864
  
    Here's the mockup:
    
    <img width="1008" alt="replication job configuration" 
src="https://cloud.githubusercontent.com/assets/12969375/23628932/edf63806-026a-11e7-949a-1224760807ac.png";>
    
    So, no tab on this page. And instead of "Replication > New Replication" or 
the proposed "Replication-Job Details," I think "Job Configuration" in the 
header will be a better descriptor.  Because you can edit an existing job on 
this page, "New" isn't exactly correct (though I know an edited job is just a 
new job on the back of a stopped one).
    
    I know you're mid-way through this, and the beta doesn't necessarily 
reflect the most recent work, so apologies if this is already on your radar, 
but the local source/target dropdown component doesn't yet match the length of 
the longer dropdown field.
    
    Also, I realized that we can now remove some of the text from our Verify 
Deletion error messages, now that replicator and _replicate have separate tabs. 
 Also, we need to change some of the button text, as _replicate deletions don't 
involve deleting a document.
    
    Here are the messages, varying on whether deletion is triggered through the 
bulk selector, or in the table-row trashcan icons: 
    
    <img width="428" alt="replication - verify single deletion dialogue" 
src="https://cloud.githubusercontent.com/assets/12969375/23630045/6315d04e-026e-11e7-9f24-5f5eab144b50.png";>
    <img width="428" alt="replication - verify deletions dialogue" 
src="https://cloud.githubusercontent.com/assets/12969375/23630044/6314733e-026e-11e7-8c5a-475f3cf9c6b6.png";>
    
    Thanks for the work on this. It's looking great.



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