rename: aVarName to: aName in: aClass self rename: aVarName to: aName in: aClass renameAccessors: false ^^^^^ (false makes sure that there is no renaming).
On 26 Feb 2015, at 16:12, stepharo <stepharo@free.fr> wrote:
This was a BAD IDEA to rename naively accessors when we rename an instance variable. Now I cannot use instance renaming because of the ripple effects I do not control. And I just got an emergency evaluator when I simply wanted to rename an instance variable in ButtonModel :(
Mark do you know if your changes go integrated? His changes where integrated, the undo of this not. Yes, we should remove this...
I did not get the undo. But in my image renaming a variables renames the accessors and more. To work I modified to put false instead of true. rename: aVarName to: aName in: aClass self rename: aVarName to: aName in: aClass renameAccessors: false I can prepare a slice to either remove the behavior or at least turn it off.
Because now I will work without refactoring and I have all the spec classes to change. Not fun.
Stef