Why "Do Refactor"?
Why is it that by default Idea forces the user to confirm whether or not they want to refactor? I must uncheck "Preview usages to be changed" from multiple (at least more than one) dialogs before it gets to a state where it stop pestering me for confirmations. Additionally, Idea has always (for all versions of Idea) gotten into situations where the preview checkbox is not checked but it still previews the changes and doesn't perform the refactoring without showing me a useless list that I've never read and never will. I never want to preview changes. If I don't like what it end up doing, I just undo it. I think this process needs to be streamlined to a global setting (that is fully respected) and I personally think it should be disabled (no previews) by default.
Please sign in to leave a comment.
I think it's appropriate for helping users who are new to refactoring to understand what it is and how it works in IDEA.
because refactoring strings and non java files is not exact science you
definetely want to preview those cases
"Kirk Woll" <kirk@digimax.com> wrote in message
news:10856390.1073434109257.JavaMail.itn@is.intellij.net...
they want to refactor? I must uncheck "Preview usages to be changed" from
multiple (at least more than one) dialogs before it gets to a state where it
stop pestering me for confirmations. Additionally, Idea has always (for all
versions of Idea) gotten into situations where the preview checkbox is not
checked but it still previews the changes and doesn't perform the
refactoring without showing me a useless list that I've never read and never
will. I never want to preview changes. If I don't like what it end up
doing, I just undo it. I think this process needs to be streamlined to a
global setting (that is fully respected) and I personally think it should be
disabled (no previews) by default.
If you've unchecked the "Preview usages to be changed" box, IDEA still
displays the preview when it finds usages in strings and comments. IDEA has
no way of knowing whether these are things that should actually be changed
or not, so it forces you to decide. Fortunately it makes it pretty easy to
say which should and shouldn't be refactored. Plus you can also tell it not
to look for occurrences in strings and comments, which will avoid the problem.
Vil.
Kirk Woll wrote:
--
Vilya Harvey
vilya.harvey@digitalsteps.com / digital steps /
(W) +44 (0)1483 469 480
(M) +44 (0)7816 678 457 http://www.digitalsteps.com/
Preview also gives you a visual record of what will/has changed, so you
can go do things to the changed classes if you need to for instance.
As this is a job you only have to do once (and sounds like you've done
it) why do you want it to be done for you by default?
N.
Kirk Woll wrote:
understand what it is and how it works in IDEA.
Yes, this was the real intent. Although most of experienced users will
probably turn preview off, it seems that showing preview by default help
novice users to understand how refactorings work.
--
Valentin Kipiatkov
Chief Scientist, Vice President of Product Development
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Keith Lea" <keith@cs.oswego.edu> wrote in message
news:4949695.1073438920836.JavaMail.itn@is.intellij.net...
understand what it is and how it works in IDEA.