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

docs: Move Steep in Ruby Section & minor cleanups #2377

Merged
merged 5 commits into from
Dec 21, 2023

Conversation

themilkman
Copy link
Contributor

As always, please feel free to request changes or do them on your own if I missed something.

Thanks & cheers!

Co-authored-by: Предраг Николић <[email protected]>
"clients": {
"steep": {
"enabled": true,
"command": ["bin/steep", "langserver"],
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this supposed to be a relative path? Because it is here but since this is a global server configuration, it's not likely to work.

Comment on lines 547 to 550
1. Add the `steep` gem (see [github:soutaro/steep](https://github.com/soutaro/steep)) into your Gemfile and install it

```sh
bundle install
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know the ruby ecosystem but why are those instructions say to add to "gemfile" while instructions for other servers say to use gem install? Is it because this approach is local to the project while gem install is for installing globally? If so then shouldn't we recommend to install globally in this case also?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've been thinking about this, too. I already had a commit prepared but skipped it as I did not want to change too much in the scope of this PR. Especially that no other Ruby LSP mentions the "add it to your project" way, which it is when adding it to the Gemfile - I also thought it should be changed. I am not sure if dropping this & migrate it to the global way wouldn't be the best solution.
Generally speaking, in order to try steep & test it, locally I did the gem install way to verify it works - and not the described.
Shall I rewrite it to align it with the others?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would say that project-specific setup should be combined with a project-specific configuration. Unless there is something specific about this server that makes it more suitable for project-specific use, I'd suggest following other setups for global server.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just pushed a commit with a global setup configuration.

@rchl rchl merged commit 7af44d6 into sublimelsp:main Dec 21, 2023
@themilkman themilkman deleted the docs_update_steep branch December 22, 2023 07:56
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

Successfully merging this pull request may close these issues.

3 participants