• 0 Posts
  • 6 Comments
Joined 5 months ago
cake
Cake day: July 15th, 2024

help-circle

  • now i’m confused about why solargraph, which is said to be mature, can’t do that

    It’s important to note that ruby-lsp is made by Shopify, and is currently used in-house by the company. The resources they can invest into ruby-lsp both in terms of development man-power and project management is naturally going to be higher than the community developed solargraph.

    and also i just realized it when i used map instead of select; the methods appeared.

    That’s strange, but Enumerable#map and Enumerable#select have different uses. One is used to execute a block across a collection of elements, while the other constructs a new collection based on the block passed to a collection and the results of evaluating that block against each element.

    wanna try RubyMine but i already comfortable in neovim. since RubyMine is an IDE i think my machine can’t handle that lol.

    I use RubyMine on my desktop and it’s a very solid development experience. I’ll say that if your machine can’t quite handle RubyMine, VS Code(ium) is a nice alternative with the solargraph or ruby-lsp plugins. I don’t know if they’ll have the same completion issue as neovim though.



  • Interesting. I’ve had this issue before and I’ve concluded that both LSP gems don’t really have a great solution to this problem. It crops up for me in both some code blocks and nested blocks. The solargraph maintainers have provided a solution for user-defined Classes here, but that’s not really applicable in your case.

    Being frank, I would open an issue with both LSPs with your code example to get a better idea of what’s actually going on here and what potential solutions you can explore. Sorry I couldn’t offer more insight here


  • I used solargraph for a really long time and it mostly suited all my needs, but I’ve seen it chew through memory in resource-bound environments (laptops with > 8GB RAM). Solargraph is very mature and is actively developed as of today. I’d say it’s still a very fine choice for anyone needing some LSP features in a text editor.

    Personally, I switched to ruby-lsp some time back and haven’t needed anything else but my requirements aren’t the norm. I spend a lot of time in a terminal with tmux, vim/helix (which has ootb support for solargraph), and a handful of monitoring tools.

    Overall, I would say solargraph should fit the bill for most users. Ruby-LSP is great if solargraph isn’t cutting it for you in some way.