Search results for #undef_method
So I've come to believe that #undef_method is actually violating the Liskov's Substitution Principle in this instance. Is it better my Repository doesn't inherit from the BaseRepository, or is it OK to use #undef_method :create to prevent calls to the inherited #create class?
“If S is a subtype of T, then object of the type T in a program may be replaced with objects of type S without altering any of the desirable properties of that program.” So in #Ruby a child has to respond to the same messages as its parent? #undef_method prevents this, right
I decide to complete the challenge without inheritance and worry about refactoring and after all the tests are green. However some found the #undef_method in #ruby, which is pretty cool in that I didn't know you could do that. Question: Isn't undef_method violating the LSP?
@dkubb @lsegal Is the #undef_method necessary there if you're going to inevitably do #define_method?
@devynci that’s unimportant when I’m passing it to #define_method (storing a method via #instance_method, #undef_method’ing it, restoring)