Skip to content

Standard Ruby does not detect Gemfile inside workspace folders #29

@eelmoni

Description

@eelmoni

AS IS

  • I open my .code-workspace file in a new VS Code window that includes multiple folders.
  • The Standard Ruby extension fails to initialize. It does not detect the Gemfile located in one of the workspace folders (even though the folder is correctly listed in the workspace and the Gemfile is 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": true is enabled.

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 Gemfile at the workspace root, not per folder.
  • Tested on:
VS Code version 1.100.2
Sonoma 14 macOS
Standard Ruby extension version 0.0.16

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions