-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix bundler env #2595
Fix bundler env #2595
Conversation
I've signed the CLA! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the PR! We definitely missed this.
We should add a test for this to prevent regression. This test isn't exactly the same, but it also mutates project specific Bundler settings.
Can we please add a test case that configures any Bundler setting as an array so that we can confirm that the environment is mutated properly?
34c23e3
to
1d04d02
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! Let's just ensure we invoke tr
too and we can ship
219eb88
to
82e4077
Compare
82e4077
to
c6b5721
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the contribution!
Thank you for creating Ruby LSP and quick responses! |
Motivation
Bundler has array configs like
BUNDLE_WITHOUT
andsettings[e]
returns array that later converted to string incorrectly (e.g.'[:development, :test]'
, but must be'development:test'
). Because of that bundler tries to install all gems in Gemfile, whenruby-lsp
is not included in your application's GemfileImplementation
Automated Tests
Couldn't find any related tests, so tests are missing.
Manual Tests
You need to have a group of gems in your Gemfile. Then you should run
bundle config set without 'YOUR_GROUP'
. And you should not have gems in this group installed after the LSP server starts