Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Streamline extension contributions to the remote indicator #8016

Closed
joyceerhl opened this issue Feb 9, 2023 · 3 comments
Closed

Streamline extension contributions to the remote indicator #8016

joyceerhl opened this issue Feb 9, 2023 · 3 comments
Labels
containers Issue in vscode-remote containers github-codespaces ssh Issue in vscode-remote SSH wsl Issue in vscode-remote WSL

Comments

@joyceerhl
Copy link

joyceerhl commented Feb 9, 2023

Guidelines for extensions contributing entries to the remote indicator:

  • Reduce the total number of actions contributed per remote, in order to ensure that as many remotes' actions are visible at a glance as possible
    • When in a local window there should be at most 3 actions per remote
    • When in a remote window, the relevant remote category should remain sorted to the top, and there should be at most 5 actions per remote
  • Remote names should be consistent where possible
    • Where it makes sense, remotes should use consistent verbs ('Connect', 'Create' etc)
    • Remote indicator actions should be suffixed with ... when they will trigger a multistep flow
  • Getting Started and Configure actions for each remote shall be surfaced as quickpick buttons instead of being listed as quickpick items to save space in the list, we will introduce API for this
  • Getting Started actions should ideally open each remote's walkthrough in-product instead of redirecting to docs
  • Remotes which have separate commands like 'Connect to _' and 'Connect to _ in New Window' should consolidate these actions and respect "window.openFoldersInNewWindow", or we can add support for alt modifiers to open in a new window
Window Current remote indicator contents Proposed remote indicator contents
Local empty window image image
Local folder image image
Dev container image image (Additional offscreen items: Install Additional Remote Extensions, Close Remote Workspace)
Codespaces image image
Remote Repositories image image (Additional offscreen items: Connect to Host..., Open SSH Configuration File... Connect to Tunnel, Install Additional Remote Extensions, Close Remote Workspace)
WSL image image (Additional offscreen items: Install Additional Remote Extensions, Close Remote Workspace)
Tunnels image image (Additional offscreen items: Close Remote Workspace)
SSH image image
@rjra100
Copy link

rjra100 commented Mar 3, 2023

Suggestion: rather than deciding what 3 actions are deemed worthy of inclusion in the remote indicator, allow it to be configured. Different situations have different workflows: for example, I almost never use any of the three "worthy" actions from Dev Container, but I regularly want Open Folder in Container and Rebuild Container.

@roblourens
Copy link
Member

Can this be closed @joyceerhl?

@joyceerhl
Copy link
Author

Yes, thanks

@microsoft microsoft locked and limited conversation to collaborators Feb 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
containers Issue in vscode-remote containers github-codespaces ssh Issue in vscode-remote SSH wsl Issue in vscode-remote WSL
Projects
None yet
Development

No branches or pull requests

3 participants