See docs/troubleshooting.md Other Notable Extensions
Legacy Configurationĭocs/legacy.md contains the documentation around the legacy functionality Troubleshooting Each option is associated with a name and description. Reviewing the linting, formatting, and environment detection docs is recommendedįor full details on configuration options, please take a look at the Ruby section in the VS Code settings UI. "ruby.format": "rubocop" // use rubocop for formatting "useBundler": true // enable reek via bundler
"useBundler": true // enable rubocop via bundler "eLanguageServer": true, // use the internal language server (see below) Legacy functionality will most likely not receive additional improvements and will be fully removed when the extension hits v1.0 Example Initial Configuration: "eBundler": true, //run non-lint commands with bundle exec See docs/language-server.md for more information on the language server. The server does not default to enabled while it is under development but it provides a significantly better experience than the legacy extension functionality. It is highly recommended that you enable the Ruby language server (via the Use Language Server setting or eLanguageServer config option). Given how dynamic Ruby projects can be (are you using rvm, rbenv, chruby, or asdf? Are your gems globally installed or via bundler? etc), the extension requires additional configuration for additional features to be available. However, these defaults do not include settings to enable features like formatting or linting. Search for ruby in the VS Code Extension Gallery and install it! Initial Configurationīy default, the extension provides sensible defaults for developers to get a better experience using Ruby in Visual Studio Code.
0 kommentar(er)
