CodingSpectator uses an ITypeRoot to capture information about code snippets. Issue #220 made us change the ITypeRoot that CodingSpectator uses to generate the code snippet. As a result, the old ITypeRoot objects the CodingSpectator computes for every processor based refactorings are no longer needed. It's a good idea to reexamine the processor based refactorings and revert the changes that are now unnecessary. There are two advantages in getting rid of the code used to compute ITypeRoot objects in individual refactoring processors:
By reverting some of the changes, the changes made by CodingSpectator become easier to understand.
Making the changes of CodingSpectator to Eclipse smaller lowers the odds of changing the behavior of Eclipse and introducing bugs.
CodingSpectator uses an ITypeRoot to capture information about code snippets. Issue #220 made us change the ITypeRoot that CodingSpectator uses to generate the code snippet. As a result, the old ITypeRoot objects the CodingSpectator computes for every processor based refactorings are no longer needed. It's a good idea to reexamine the processor based refactorings and revert the changes that are now unnecessary. There are two advantages in getting rid of the code used to compute ITypeRoot objects in individual refactoring processors: