Andy Waite comments

Results 394 comments of


                                            Andy Waite

Add methods generated through metaprogramming to the index

@vinistock are you thinking this would be a new kind of `Entry`, e.g. `Entry::DynamicMethod` ?

Add methods generated through metaprogramming to the index

Add-ons can now contribute to the index: https://shopify.github.io/ruby-lsp/add-ons.html#enhancing-features

Test PostgreSQL ActiveRecord adapter types

That's interesting, normally you would use a separate image for postgres, e.g.: https://github.com/rails/rails/blob/e7c0592cd2944caf9d70c3fabe9ec6877f1f951b/railties/lib/rails/generators/rails/app/templates/github/ci.yml.tt#L83-L92 If we may need to test against different versions of postgres then the image approach would be...

Test against Rails 8

[Confirmed that we will drop Rails 7.0 support.](https://github.com/Shopify/tapioca/pull/2161#issuecomment-2605306252)

Hover Definitions for Ruby Keywords

> A false value usually indicating “no value” or “unknown”. I'd suggest "falsey" rather than false.

Add a list of test tools?

A couple to start things off (for Ruby): * https://github.com/aespinosa/minitest-junit * https://github.com/sj26/rspec_junit_formatter

Correct configuration file from general index.yml in root of project with relocating it to already existing .ruby-lsp folder.

We're discussing if this is the right approach: https://github.com/Shopify/ruby-lsp/pull/1434#issuecomment-2018723331

Correct configuration file from general index.yml in root of project with relocating it to already existing .ruby-lsp folder.

We are planning to deprecate the `.index.yml` file: https://github.com/Shopify/ruby-lsp/issues/2156

Rogue ruby-lsp related processes even after VS Code is quit

:wave: There are various things that could potentially cause this, but we'd really need a consistent reproduction case to investigate. (btw I corrected the spelling in the PR title to...

Rogue ruby-lsp related processes even after VS Code is quit

> To the point of processes running after VS Code has been terminated: Isn't there a mechanism to ensure that child processes are properly terminated? Depending on how the extension...