Skip to content
This repository has been archived by the owner on May 11, 2022. It is now read-only.

More clearly illuminate CLI commands to avoid unexpected results #31

Open
bfitzpat opened this issue Jan 22, 2020 · 1 comment
Open

Comments

@bfitzpat
Copy link
Collaborator

Currently when we send text to a VS Code terminal, we explicitly hit a hard return afterwards so it is automatically executed. This makes it difficult for the user to discern the intention of any CLI commands we are helping them to execute.

We need to offer some better guidelines and options for how to handle this for the user to avoid any confusion or irrevocable changes to their system.

@bfitzpat
Copy link
Collaborator Author

We can do this in one of a few ways or offer multiple ways to handle it ahead of time...

Once concern seems to be with the links currently labeled "Click this" instead of clearly delineating what the link does.

Currently we have a tooltip that shows some text that can include the command line. The tooltip offers some help, but the user may not know to hover over to get the additional clarification.
image

Perhaps we shouldn't automatically hit return for the user, instead putting focus on the terminal and having them explicitly hit Enter once they see what they're invoking at the command prompt.

Or maybe we include some javascript/css that shows a widget that expands to show the command line prompt and requires a second, explicit click to invoke the command.

I'd like to avoid the ubiquitous "Are you sure? Y/N" questions that plagued UX in the 1990s and 2000s if at all possible. But we should be able to work around this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant