Consolidate primary action button labels on workspace start
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Problem to solve
In https://github.com/gitpod-io/gitpod/pull/8783, we've consolidated the editor options by having a single array of options including the browser version of VS Code which is the default and fallback option as well as other options for desktop editors or IDEs like VS Code and JetBrains' IDEs.
- When using the latest release for VS Code, the primary action button label reads: Open in VS Code Insiders on Desktop
- When not using the latest release for IntelliJ IDEA, the primary action button label reads: Open in IntelliJ IDEA
- When using the latest release for IntelliJ IDEA, the primary action button label reads: Open in IntelliJ IDEA
Proposal
Following up the relevant discussions[1][2] from #8783, to resolve the inconsistency above but also provide a better button label that treats desktop editors as first-class citizens we could do rename the button labels with the following structure:
Open [[EDITOR]] [[LATEST_RELEASE]]
For example, we could have Open VS Code, Open VS Code Insiders, Open IntelliJ IDEA, Open IntelliJ IDEA EAP, etc.
Cc @mustard-mh @akosyakov @loujaybee
Contributor guide
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
Locate the workspace start UI and the editor-options data introduced in PR #8783, then inspect how primary action labels are selected for VS Code and IntelliJ IDEA. Done means the labels consistently follow the proposed “Open [EDITOR] [LATEST_RELEASE]” structure, including desktop and latest-release variants.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100