You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I haven't verified this yet, but @paracycle told me that if one gem defines a method, and another gem overrides that method via a prepend, the prepended method will be incorrectly written to both gem RBIs.
Example:
# in gem foo
class Foo
def foo; end
end
# in gem bar
module Bar
def foo; end
end
Foo.prepend(Bar)
Tapioca will write bar's foo method to foo's gem RBIs, which is fine if they have the same signature, but not great if the prepend changes the method signature.
The text was updated successfully, but these errors were encountered:
I haven't verified this yet, but @paracycle told me that if one gem defines a method, and another gem overrides that method via a prepend, the prepended method will be incorrectly written to both gem RBIs.
Example:
Tapioca will write
bar
'sfoo
method tofoo
's gem RBIs, which is fine if they have the same signature, but not great if the prepend changes the method signature.The text was updated successfully, but these errors were encountered: