Github user justin-mcdavid-ibm commented on the issue:
https://github.com/apache/couchdb-fauxton/pull/669
Hey Ben,
I'm testing this, and it's awesome. Great work on this. It's a big
improvement.
There are a couple of things I'm seeing that we probably should tweak.
The "Select source" and "Select target" in-field explanatory test should be
gray, though values selected through those dropdowns should remain the color of
regular text.
When you specify a custom replication doc ID, it has to be a new ID (folks
might think they can specify an existing doc-- which causes a conflict), so we
should elaborate on the explanatory text as [Custom, new ID (optional)]. Also,
because you can't use the same custom ID for multiple jobs, can we add a clear
(x) inside the custom ID field, so that after starting a replication job, users
can easily clear just that field if they're reusing selected dbs or remote
creds?
If possible, we should remove the verification step where the account
password is entered. I'm not sure why it's a requirement. If we do keep it,
the button should be "Start Replication" rather than "Continue Replication,"
and we should specify which password is required, because it could be
interpreted as a remote account's password.
Icing, but after selecting from a dropdown, can we make focus automatically
change to the following object?
If there are illegal characters (spaces, prohibited symbols), or if the db
name starts with something other than a lower-case letter in new-database-name
field, can we disable the replicate button? I was able to "trigger" a
replication from a local db to a new one called "spa ces" which then failed.
Thanks for your work on this.
---
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.
---
