solargraph VS hexpm

My favorite typing solution so far in ruby is Solargraph https://solargraph.org/.

Solagraph: https://solargraph.org

Yay! For those who don’t know solargraph provides a language server protocol (LSP) for Ruby so that your IDE (like vscode) can know more about the code you’re writing https://solargraph.org/.

If you're looking for IDE-level language assistance, I can't help you, but since you mentioned nvim: I use regular vim with CoC / Conquer of Completion (vim plugin; LSP server, may not strictly be necessary for nvim), Solargraph (Ruby Gem; language server), and Rubocop (also a Gem) for linting. I previously/still use ALE (vim plugin; Asynchronous Lint Engine) because I haven't gotten CoC+Solargraph to play nice with Rubocop, probably due to something silly.

https://github.com/neoclide/coc.nvim

https://solargraph.org/

https://rubocop.org/

https://github.com/dense-analysis/ale

My impression with all of this running under MacVim... it's plenty responsive. It can take a while for Solargraph to index everything on startup if you're working in a big project; once it loads, it's snappy. (There's probably a way to cache that startup scan.)

I am trying to use lsp-mode for ruby via solargraph and for Rails era templates using web-mode via lsp-tailwindcss and both seems to kinda sorta work but neither one is really giving me all the features that I see that others have.

https://github.com/castwide/solargraph Seems to be the most mature/developed one. Slow on my system, bad documentation. Language docs are shipped as "cores" you imperatively download that float around in your home directory; this is messy and prone to failure. Doesn't have any docs for versions of ruby past 2.7.

I have recently installed Solargraph and can see that when I open a Ruby file that the LSP is attached to my buffer via `LspInfo`. However whenever I am trying to do some very basic completions or see what kind of methods are available for an object, literally nothing happens. What I am aiming for is something like on the official Solargraph website: https://solargraph.org/

If you use Vim or Neovim, you can display RuboCop's diagnostics through coc.nvim. You need to install the Solargraph language server (gem install solargraph), followed by the coc-solargraph extension (:CocInstall coc-solargraph). Afterwards, configure your coc-settings.json file as shown below:

The builtin LSP works well with solargraph to provide autocompletion.

Sorbet and/or RBS seems like they may be the future given how popular typescript is with JS programmers these days. There are some other projects that assist programmers without relying on formal type definitions in the source or shadow typing files:

Solargraph combines inference and insight from YARD docs (standard for many gems, plus Castwide has written more YARD for the standard library) to make some pretty good guesses. Crucially it has plugins that add the insights from popular gems with static analysis (e.g. reek, rubocop). I maintain solargraph-rails, which parses your Ruby to make guesses about (surprise) Rails.

The typeprof gem can help IDE plugins make typing guesses based on your tests. This project is interesting to me because it's going into Ruby 3.1 so I think it reflects awareness from the core ruby team that many programmers are not ready to add types to their code.

solargraph: https://github.com/castwide/solargraph

I was thinking of porting this library to Elixir. But first, I searched on hex.pm and Surprising. I found two packages that support merging tailwind classes: twix and tails

I often reference https://github.com/hexpm/hexpm which is the code behind hex.pm.

Feel free to take a look at the package manager and let me know if there are any libraries that you need that are missing. https://hex.pm/

I can assure you I'm not spending my time inventing new libraries. In the past 3 or so years of working in Elixir there have been maybe 2 or 3 cases where I was looking for a library and couldn't find a suitable one. Writing my own code to cover those cases took a few hours. This should hardly be a deal breaker for anyone if you take into account dozens, maybe even hundreds of hours the ecosystem could save you in the long run if your project is a good fit for it.

Before getting started you need to have both Elixir, the Hex package manager, the PostgreSQL relational database server and Node.js installed on your local computer to be able to follow through this guide.

We can then look at that function and see that ultimately it calls Supervisor.start_link(...) on a bunch of children. That means that one process's only job is to start up all those child processes and "supervise" them, meaning if any of them crash it will be notified and be able to handle that. I note that one of the processes runs the code in the module Hexpm.RepoBase which means it's in charge of managing database connections, and one runs the code in the module HexpmWeb.Endpoint which is the process in charge of managing the Phoenix side of things, handling incoming requests, spinning up new processes to handle each one, and directing them to the right controllers and stuff. Then there's a bunch of other modules listed, for things like rate limiting, billing reports, and other stuff. You can look in the codebase for those listed modules if you're interested, but the thing to note is that by putting the module name there, what happens is the supervisor will spawn a new process and run the start_link function of that module within that new process.

I was looking for a solution to run tests automatically every time I save any changes. The best way so far for me is the following hex package:

API server and website for Hex https://github.com/hexpm/hexpm

Dependency Current Latest Status bunt 0.2.0 0.2.0 Up-to-date cowlib 2.11.0 2.11.0 Up-to-date credo 1.6.1 1.6.3 Update possible db_connection 2.4.1 2.4.1 Up-to-date decimal 2.0.0 2.0.0 Up-to-date earmark_parser 1.4.19 1.4.20 Update possible postgrex 0.15.13 0.16.2 Update not possible To view the diffs in each available update, visit: https://hex.pm/l/AsY7q

Now it’s time to decide on a name for your package. In this guide I will be creating a new Ueberauth package. If you were to go on http://hex.pm and look at other Ueberauth packages, you notice there is a certain pattern followed. This will make the decision easy for us on what to call our Uberauth package that will implement the Patreon OAuth flow.

Go to the website https://hex.pm and search for the faker library to grab the latest version, so you can copy that to your mix config file, at the time of the making of this tutorial the latest version is 0.17.0, add the following to your project dependencies inside your mix.exs file: