On 07/28/2017 08:29 AM, Denis Kudriashov wrote:
Hi Thierry
2017-07-28 15:01 GMT+02:00 Thierry Goubier <[email protected]
<mailto:[email protected]>>:
Hi Denis,
So it's post-refactoring that you scope, not pre-refactoring?
post-refactoring: refactor, then restrict (scope) to what it is applied
pre-refactoring: restrict (scope) first, then refactor, then apply
Post/pre distinction looks strange because they both not change anything
in image.
But I understand what you are talking about. So it will be
pre-refactoring on current scope (full image by default).
And change browser will allow choose different scope which will
reevaluate refactoring again and update shown changes.
I haven't been keeping up on the discussion so I may be way off...
However, if you are using the scoping that is already built into the
RB's refactorings, then it is pre-refactoring (i.e., they don't look at
code outside the scope).
BTW, if you use post-refactoring, then things like safe remove method
wouldn't work since calls outside the scope would cause the refactoring
to abort without removing the method.
John Brant
