[GitHub] couchdb-fauxton issue #669: [WIP] Replication page update

[benkeen <gi...@git.apache.org>]

Github user benkeen commented on the issue:

    https://github.com/apache/couchdb-fauxton/pull/669
  
    TODO - notes from Justin:
    
    - In-field explanatory text should be gray +1
    - Text on the replication button should be \u201cStart Replication\u201d +1
    - The in-field explanatory text for Remote Sources and Targets should be https://$REMOTE_USERNAME:$REMOTE_PASSWORD@$REMOTE_SERVER/$DATABASE - 
    
    [discussion: oooffff... that's awful verbose. I think REMOTE_* is implicit, no? I mean you already picked "remote source" / "remote target". Don't want to bludgeon them over the head with it. Oddly clarity becomes less clear here.
    I'd be worried about some mistakenly thinking they needed to enter the current account's username and password. Maybe just drop the REMOTE_ on SERVER?]
    
    - Increase the widths of all dropdowns. \u201cExisting remote database\u201d gets cut-off after selection (in FF, but not Chrome, I see). +1
    - The replicate button activates after fields have been clicked on, but not before information is actually entered. Can we have the replication button activate only after the fields are populated? +1
    -  There doesn\u2019t appear to be any checking for the pre-existence of a \u201cnew\u201d database. I selected \u201cnew local database,\u201d and used the same DB for source and target.  Can we put in check in to make sure that users aren\u2019t accidentally overwriting existing DBs? I\u2019m assuming that there are back-end safeguards, but my test-replication job didn\u2019t throw any errors. +1
    - Can we leave the replication button inactive if the DB listed as an existing local source doesn\u2019t actually exist?  I can enter an db that doesn\u2019t exist and still trigger replication. Same for non-existing local targets. +1
    
    Other:
    - A source database that is open to/readable by the public does not require $USERNAME and $PASSWORD in its URL, right? Or do they all now require authentication (I remember something about this in your chats with Bob)? - Not sure... this bit's hard. :) In my trial and error I found you usually had to enter it, but I'll confirm.



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