"Change All" intention enhancement?

Has any more consideration been made to allowing the "Change All" intention
to operate on more than just local variable names?

There seem to be lots of times where I'm pasting some code in from another
place where the only thing that needs to change is the name of a type, for
example. So the type name "Foo" is in red everywhere, and it sure would be
nice to have the intention lightbulb pop up when I click on that unresolved
identifier, and then be able to select "Change all Foo" to change all
references to Foo that are unrecognized, to something like Bar.

Will that make it into 1.5? Not a week goes by that I don't need to "change
all" for something OTHER than a local variable name.



3 comments
Comment actions Permalink

Hello Paul,

Thank you for your feedback!
Unfortunately, we will not be able to insert class suggestions into "Change
All" for 1.5 (it will work too slow for a quick fix), but we will most probably
add this functionality in 2.0.

Has any more consideration been made to allowing the "Change All"
intention to operate on more than just local variable names?

There seem to be lots of times where I'm pasting some code in from
another place where the only thing that needs to change is the name of
a type, for example. So the type name "Foo" is in red everywhere, and
it sure would be nice to have the intention lightbulb pop up when I
click on that unresolved identifier, and then be able to select
"Change all Foo" to change all references to Foo that are
unrecognized, to something like Bar.

Will that make it into 1.5? Not a week goes by that I don't need to
"change all" for something OTHER than a local variable name.






0
Comment actions Permalink

Hrm. Not sure what would be 'too slow'. It already knows that it's an
unresolved identifier. Can't it just put an intention bulb out there with
the "Change All" option, and allow me to change ALL unresolved identifiers
with that name to whatever I want? It's really nothing more than a
restricted "search and replace", isn't it? What would be slow? It doesn't
have to look up anything that it doesn't already know...


"Andrey Simanovsky" <ands@intellij.com> wrote in message
news:23980632443590013462504@news.intellij.net...

Hello Paul,

>

Thank you for your feedback!
Unfortunately, we will not be able to insert class suggestions into
"Change All" for 1.5 (it will work too slow for a quick fix), but we will
most probably add this functionality in 2.0.

>
>> Has any more consideration been made to allowing the "Change All"
>> intention to operate on more than just local variable names?
>>
>> There seem to be lots of times where I'm pasting some code in from
>> another place where the only thing that needs to change is the name of
>> a type, for example. So the type name "Foo" is in red everywhere, and
>> it sure would be nice to have the intention lightbulb pop up when I
>> click on that unresolved identifier, and then be able to select
>> "Change all Foo" to change all references to Foo that are
>> unrecognized, to something like Bar.
>>
>> Will that make it into 1.5? Not a week goes by that I don't need to
>> "change all" for something OTHER than a local variable name.
>>
>
>
>
>



0
Comment actions Permalink

Hello, Paul,

I have misunderstood your primary point. I see it clearly now, but the timeframe
of 1.5 version does not allow adding functionality at present. We definitely
will add replace unresolved identifier in 2.0 (BugTraker request 5870).

Hrm. Not sure what would be 'too slow'. It already knows that it's
an unresolved identifier. Can't it just put an intention bulb out
there with the "Change All" option, and allow me to change ALL
unresolved identifiers with that name to whatever I want? It's really
nothing more than a restricted "search and replace", isn't it? What
would be slow? It doesn't have to look up anything that it doesn't
already know...

"Andrey Simanovsky" <ands@intellij.com> wrote in message
news:23980632443590013462504@news.intellij.net...

>> Hello Paul,
>>
>> Thank you for your feedback!
>> Unfortunately, we will not be able to insert class suggestions into
>> "Change All" for 1.5 (it will work too slow for a quick fix), but we
>> will
>> most probably add this functionality in 2.0.
>>> Has any more consideration been made to allowing the "Change All"
>>> intention to operate on more than just local variable names?
>>>
>>> There seem to be lots of times where I'm pasting some code in from
>>> another place where the only thing that needs to change is the name
>>> of a type, for example. So the type name "Foo" is in red
>>> everywhere, and it sure would be nice to have the intention
>>> lightbulb pop up when I click on that unresolved identifier, and
>>> then be able to select "Change all Foo" to change all references to
>>> Foo that are unrecognized, to something like Bar.
>>>
>>> Will that make it into 1.5? Not a week goes by that I don't need to
>>> "change all" for something OTHER than a local variable name.
>>>



0

Please sign in to leave a comment.