Rename a type or method is not supported.

[coocood]

I don't know if this is easy or not.

it requires to search the entire project and determine if the matched code is that identifier.

but rename is so important, i do rename all the time to improve the readability of the source code.

[mtoader]

Yea ... renaming would be good to have but it's tricky since the resolving is not up to par yet.

[coocood]

I took a look at the plugin development documents today, it was said that the way "rename" is working is not much different than "find usage", and the "find usage" is already implemented. So I guess it is not very difficult for you.

Do you have a plan to support this feature in the near future?

[mtoader]

I do have plans to support it but it's not easy because for example find usages doesn't really work properly right now.

This is partially caused by the way the parsing works now and this needs to be redone.

I have some work started on that but is not trivial.

So any feature that is involved (and has the potential of being damaging as rename is for example) will have to wait in line ;).

Mihai

[duclosm]

Any update about this issue ?
I think it's important to be able to rename methods and types.

[mtoader]

Not yet. We (actually @dlsniper) are trying to stabilizing the current build and then try to work on this.

[coocood]

@mtoader How is the GrammarKit branch going, Would it be easier to implement rename feature with GrammarKit?
I went through some refacor API. It looks very complicated.
But for variable in block scope, IDEA automatically handle it for free.

[mtoader]

Not yet ready.

[bronze1man]

+1 @duclosm

[mtoader]

That will have to wait until the formatter is done. I'm reworking the parser in the meantime. aftter that i'll redo the resolving to use absolute addresses and then we can implement renames.

[smotes]

@mtoader Do you know the status on this issue?

[glyn]

Renaming a method in an interface is partially implemented, but it can introduce a compile error because it doesn't attempt to rename "corresponding" implementation methods. Similarly for renaming an implementation method.

Anyway, I'm pleased to see this bug has been raised.

[dlsniper]

I'll migrate this one to 1.next as I'm not sure if it's that important for 1.0 release. The issue was opened for the 0.9.x branch

[dlsniper]

Type renaming is supported, as well as methods (but not from the interface itself). Closing this for now.