Add Homebrew's ruby to PATH for VSCode Ruby LSP setup
#21233
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After #21111, Homebrew's ruby was no longer added to the PATH in the
ruby-lsp-setup.shfile. This meant that all subsequent setup steps were using the wrong Ruby, leading to the wrong Gem setup being used. This PR adds ruby back to the PATH to (mostly) fix vscode.Unfortunately, the
test-profissues (see #21220) are preventing RuboCop from working out of the box, so vscode is still slightly broken. The workaround is to comment out thetest-profplugin in.rubocop.ymltemporarily. That shouldn't be necessary once the next version oftest-profis released and gets merged in.