sigs missing blocks raise errors in latest sorbet release (0.5.6341+) about sorbet-rails HOT 5 CLOSED

This is now fixed in the upstream sorbet-typed signatures, just need to update sorbet-rails to use them.

from sorbet-rails.

Thank you @connorshea for the fix! Sorbet-rails does not bundle sorbet-typed in the API (it's included for internal development only). So anyone can update their sorbet-typed with srb rbi sorbet-typed and they would get the new signature!

from sorbet-rails.

Based on my testing I'm pretty sure the fix is just to change those signatures to this?:

  sig { params(block: T.nilable(T.proc.params(arg0: Elem).returns(T::Boolean))).returns(T::Boolean) }
  def any?(&block); end

  sig { params(block: T.nilable(T.proc.params(arg0: Elem).returns(T::Boolean))).returns(T::Boolean) }
  def many?(&block); end

  sig { params(block: T.nilable(T.proc.params(arg0: Elem).returns(T::Boolean))).returns(T::Boolean) }
  def none?(&block); end

  sig { params(block: T.nilable(T.proc.params(arg0: Elem).returns(T::Boolean))).returns(T::Boolean) }
  def one?(&block); end

from sorbet-rails.

Arguably, there are methods affected like select that we may want to change in sorbet-rails though. LMK if you run into issue with select and we can discuss how we should fix it.

from sorbet-rails.

I've ran into the issue with select after upgrading sorbet-rails. Updated the rbi manually like this for now but would love for it to be fixed here.

  sig { params(args: T.untyped, block: T.untyped).returns(ReportCategory::ActiveRecord_Relation) }
  def select(*args, &block); end

from sorbet-rails.