Windows client provisioning lacks feedback w/ invalid public name
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I recently tried to provision a system with a public name including parenthesis. This resulted in the display including an unclickable button, but not providing any visible feedback on what was wrong.
After I started the CLI-based provisioning process (keybase login) there was actually a useful message provided -- but from a usability perspective that's less than ideal.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing Windows client provisioning with a public name containing parentheses, then compare the behavior with the message shown by the keybase login CLI flow. Trace the provisioning entry point and determine where visible validation feedback should appear before the unclickable button is shown; done means the invalid name produces clear feedback in the Windows client.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100