Part 3 - Add "Switch to new Web IDE" in legacy Web IDE
- Draft: Add user setting to toggle between legac... (!98295 - closed)
- ...
- Part 1 - Hide top nav with vscode_web_ide featu... (!98891 - merged)
- Part 2 - Add "use_legacy_web_ide" to "user_pref... (!98945 - merged)
Part 3 - Add alert to switch between legacy and... (!100488 - closed)- Part 3 - Add "Switch to new Web IDE" in legacy ... (!102146 - merged)
What does this MR do and why?
This MR implements part of the UX proposal in this comment. When the vscode_web_ide feature is enabled (disabled by default) and the user has use_legacy_web_ide=true (false by default), then we show an open sidebar tab, inviting the user to try out the new Web IDE (still in development).
Screenshots or screen recordings
| Feature flag off | Feature flag on | Confirm | Error |
|---|---|---|---|
 |
 |
 |
 |
How to set up and validate locally
Setup local environment:
- Start rails console with
rails c - Enable feature flag
Feature.enable(:vscode_web_ide) - Update root user's legacy Web IDE preferences
User.find(1).update!(use_legacy_web_ide: true)
Test:
- Login to root User in local environment
- Open Web IDE for any project
- The right sidebar should have a tab opened by default, prompting the user to switch to the new Web IDE
- (optional) This MR only adds the "legacy" to "new Web IDE" experience, so to go back you'll have to update the database with
User.find(1).update!(use_legacy_web_ide: true).
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #370139 (closed)
Edited by Paul Slaughter