Hi, thanks for maintaining this gem — it's a daily-driver for me.
ruby-lsp 0.27.0.beta3 has landed the Rubydex-based indexer and removed the old RubyIndexer. Since this gem's addon currently references the old API directly — for example:
IndexingEnhancement < RubyIndexer::Enhancement (indexing_enhancement.rb)
RubyIndexer::Entry::Signature.new([]) (same file)
global_state.index #: RubyIndexer::Index? (addon.rb)
…loosening the ~> 0.26.0 pin alone won't be enough; it needs a port to the new Rubydex enhancement API.
I understand 0.27 is still in beta, so you may be waiting for a stable release before tackling this. For reference, ruby-lsp-rails has shipped 0.5.0.beta1 as a prerelease compatible with ruby-lsp 0.27.0.beta2+, even ahead of a stable release.
If you could share any rough thoughts on direction or timing for 0.27 support, that would help me plan how to use the gem going forward.
Thanks!
Hi, thanks for maintaining this gem — it's a daily-driver for me.
ruby-lsp0.27.0.beta3 has landed the Rubydex-based indexer and removed the oldRubyIndexer. Since this gem's addon currently references the old API directly — for example:IndexingEnhancement < RubyIndexer::Enhancement(indexing_enhancement.rb)RubyIndexer::Entry::Signature.new([])(same file)global_state.index #: RubyIndexer::Index?(addon.rb)…loosening the
~> 0.26.0pin alone won't be enough; it needs a port to the new Rubydex enhancement API.I understand 0.27 is still in beta, so you may be waiting for a stable release before tackling this. For reference,
ruby-lsp-railshas shipped 0.5.0.beta1 as a prerelease compatible with ruby-lsp 0.27.0.beta2+, even ahead of a stable release.If you could share any rough thoughts on direction or timing for 0.27 support, that would help me plan how to use the gem going forward.
Thanks!