That seems to violate the Principal Of Least Surprise. Whether or not it ends up getting changed, I think its worthwhile entering that directly in the issue tracker. It would assist if you could bisect to isolate which commit introduced the behaviour.
cheers -ben On Wed, 20 May 2020 at 01:34, Vitor Medina Cruz <vitormc...@gmail.com> wrote: > Hello, > > When I run a refactoring, Rename Method, for example, the refactoring is > reformatting the code affected. Is it possible to configure Pharo to > refactor without reformatting code? Depending on the refactoring, the > reformat is so intrusive that make it more worth to make the refactoring by > hand. > > Regards, > Vitor >
