Improve UX of "CLI Not Installed"

[jbyrum-stripe]

When the CLI is not installed:

• Events pane items should be in disabled state -- user should not, for example, be able to click on the "Start webhooks listening" item in the "Events" pane and launch the functionality (only to later find out it doesn't work)
• Logs pane item should be in a disabled state
• Relevant items in the command palette should be discoverable (i.e., don't remove them), but disabled
• Explore a more prominent placement for the "Install CLI dialog" than the bottom right hand corner. Is it possible to make the dialog more prominent?
• "Read instructions on how to install Stripe CLI" should deep link to: https://stripe.com/docs/stripe-cli#install
• Ensure tracking of when a user tries to interact with a disabled item (not sure what flexibility we have here). We should, for example, to be able pull the # of times a disabled item was clicked / hovered over.

Bonus points:

• On hover of a disabled item, show an onhover menu with a description of the functionality. For example, if the user hovered over "Start webhooks listening", show the message: "Install the CLI to enable the forwarding of webhook events to your local machine". The purpose of this functionality is to entice users to actually install the CLI.

[vcheung-stripe]

• We can show the "Install CLI dialog" like this:
  
• Unfortunately, items in the activity bar can't be disabled due to vscode API limitations: VSCode Extension: Disable tree items when enablement clause on linked command is false microsoft/vscode#102794. I'm trying to think of workarounds for this. Even though we can't disable these items, we could still have telemetry for which command the user tried to invoke without having the CLI.

[auchenberg]

@vcheung-stripe @jbyrum-stripe

The new "welcome alert" is quite disruptive to the workflow of opening VS Code without the Stripe CLI installed. Here's a screenshot of me opening VS Code, and the first thing I see is the Stripe alert. Notice that I'm the file explorer, and I haven't even activated the Stripe view in the sidebar. This probably happens because we have changed the extension to activate on * for some reason.

I think we should re-consider this UX, and instead explore #57 which would provide a much less in-your-face-UX via WelcomeViews. Example docs: https://code.visualstudio.com/api/references/contribution-points#contributes.viewsWelcome

[richardm-stripe]

We've had a user reach out about the aggressiveness of the reminder here: stripe/stripe-php#1118, another point in favor of revisiting this UX.

[gracegoo-stripe]

Notice that I'm the file explorer, and I haven't even activated the Stripe view in the sidebar. This probably happens because we have changed the extension to activate on * for some reason.

Thanks for reporting this!

We're not activating on * but we did have some non-stripe specific events on there. I like the idea of pre-loading the extension but the prompts that end up coming up for the user is super annoying, especially if they aren't even doing anything Stripe related at the moment, and will likely just encourage them to uninstall. It also doesn't look like the loading is heavy enough to notice if we don't pre-load it.

#219

[ossigeno]

I have uninstalled this extension. I already have Stripe CLI installed by way of Homebrew. The constant popups are madness.

[jbyrum-stripe]

@gracegoo-stripe @vcheung-stripe More feedback from our user survey:

"I have the CLI installed but it keeps saying I dont in VS code. Makes the extension unusable. "

"to many alerts i have zero understanding how to use it yet"

[vcheung-stripe]

I think we should definitely implement welcome views (#57).

In addition, I've noticed on MacOS that the popup has become much more prominent since the Big Sur update. I think that should have already been reason enough to change this UX.