April 17, 2016
3:04 p.m.
The ugly way:
[ refactoring execute ] on: RBRefactoringError do:[:ex | ex resume].
I thought about this, but there are many things that could go wrong (there are about ten preconditions), and I am certainly not interested in breaking my system by accident. However after fighting a lot with refactorings I found that I would need this behavior for many other things⦠ensuring that attribute exists, that method is the same... etc. And since there is no such support in refactorings it's kind of pointless for me to use as I will need to always work around it... or maybe I could make some sort of "Ensuring" framework on top... Peter