Hacker News Reader

Comment by modernerd | Hacker News Reader

You could make it more clear that it just generates the dump command; it doesn't attempt a connection.

1. Remove the "Generate" button.

2. Move the "Generated CLI Statement" to the right of the form as a second column (at least on wider screens).

3. Pre-fill the form with dummy data so that the generated statement does not start empty.

4. Immediately update the generated statement when someone edits any form field (with an aria-live region for accessibility).

5. Consider making the password field non-editable, or omitting it but leaving a password in the output.

6. Change "We do not store your credentials. Tasks are done in your browser" to "No data is saved. View source on GitHub." with a link to the source if you feel comfortable providing it.

View on HN

Great suggestions, I’d agree with all points!

> 6. Change "We do not store your credentials. Tasks are done in your browser" to "No data is saved. View source on GitHub."

Assuming that OP has made it clearer that this website is a CLI command builder and not a dumping tool, I’d find “No data is saved” potentially confusing. To me, it would be unclear whether “data” refers to the credentials or to the underlying database data. It might also raise the concern why a command builder utility would entertain the idea of storing anything in the first place.

Maybe “Your credentials won’t leave your computer” or so?

I would solve this by not asking for the password and just putting a password placeholder in the generated command.

That could also be an option, although an additional manual step might be slightly less convenient, especially in case you want to “debug” the command (i.e., regenerate multiple times with varying parameters).

Another potential benefit of entering the PW in the field is that the generator could take care of proper escaping – think, if the password contains spaces, quotes, asterisks, $ signs, or other bash shenanigans. (That, by the way, doesn’t seem to work right now, @OP.)

Another idea could be to allow entering an env variable name instead of a value.

If you are on a dev machine iterating quickly, just set the basic credentials up in ~/.mylogin.cnf[0] and you don't need to worry about supplying those options on the command line at all.

[0]: https://dev.mysql.com/doc/refman/8.0/en/mysql-config-editor....

I'd like to add that it wasn't obvious there was a whole ultimate guide. I think brining in some of that content on the homepage would let people discover more use cases for the command.

that is some valuable feedback!

sure, we will improve the site based on your suggestion.

thank you!

Reply on news.ycombinator.com