Skip to content
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

Don’t use Bundler if bundle exec fails #296

Open
ParadoxV5 opened this issue Nov 25, 2023 · 0 comments
Open

Don’t use Bundler if bundle exec fails #296

ParadoxV5 opened this issue Nov 25, 2023 · 0 comments

Comments

@ParadoxV5
Copy link

ParadoxV5 commented Nov 25, 2023

If bundle exec fails – typically because of missing Gemfile/Gemfile.lock, but can also because of [P.S. Steep not in Gemfile or even] missing or unreachable bundle executable – the LSP shall fall back to try whichever steep executable is available – typically the one natually from gem install steep.

I believe I can similate this by overriding the steep executable choice to a small launcher script in the plugin configs.

Together with soutaro/steep#968 or an equivalent feature, this allows Steep to work out-of-the-box as an LSP with no further setup required.
(This lifts the Bundler requirement; that lifts the requirement of Steepfile in the workspace root.)
Though of course users are encouraged to set up a Gemfile and a Steepfile.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant