[Monodevelop-devel] Improving refactoring after 2.0
Lluis Sanchez Gual
lluis at novell.com
Thu Nov 6 11:09:20 EST 2008
El dc 05 de 11 de 2008 a les 11:11 +0100, en/na Mike Krüger va escriure:
> Hi
>
> After the next release I want to improve refactoring.
> Currently we only have rename as refactoring operation. Generally I want
> to do refactoring a bit different than it is now.
>
> I want a refactoring infrastructure that allows the user to preview all
> changes that are done in the refactoring step (see eclipse for an
> example).
Notice that change previewing for the rename operation can be done with
the current infrastructure. It's a matter of finding the references,
displaying them and do the replace when the user clicks on OK. The API
supports that, although we haven't implemented the GUI.
>
> I'll need to extend/change the current refactoring infrastructure for
> this. And one of the goals for the new one is: unit test support. The
> new code completion infrastructure is tested with unit tests and I think
> that this has improved the code completion correctness greatly.
>
> Any thoughts/inputs here ?
I'd like to see a high level design of the API to get an idea of how you
plan to improve the refactoring infrastructure.
Thanks!
Lluis.
More information about the Monodevelop-devel-list
mailing list