-
Notifications
You must be signed in to change notification settings - Fork 7
Open
Labels
bugSomething isn't workingSomething isn't working
Description
AS IS
- I open my
.code-workspacefile in a new VS Code window that includes multiple folders. - The Standard Ruby extension fails to initialize. It does not detect the
Gemfilelocated in one of the workspace folders (even though the folder is correctly listed in the workspace and theGemfileis valid). - As a result, the extension logs:
[client] Disabling Standard Ruby extension, because standard isn't included in the bundle
TO BE
-
When I open a multi-folder workspace (
.code-workspace) in VS Code, the Standard Ruby extension should detect and use the Gemfile present in each folder independently (or at least in the folder where a .rb file is being edited). -
It should initialize correctly as long as:
- The folder has a valid
Gemfile. - The standard gem is included and installed.
"standardRuby.enableViaGemfile": trueis enabled.
- The folder has a valid
Notes
- The issue does not occur when opening the same folder directly (outside of the workspace).
- It seems like the extension only checks for a
Gemfileat the workspace root, not per folder. - Tested on:
VS Code version 1.100.2
Sonoma 14 macOS
Standard Ruby extension version 0.0.16
tasandberg and hoblin
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working