StéphaneDucasse
StéphaneDucasse
We should fix the rule description.
It looks like the logic got lost in the migration to the new architecture.
- RBPullUpMethodTransformation should support the pull up even when behavior is modified - but it should not produce broken code. Code can be broken when: - Refer to instance variables...
``` A >> foo ^ self subclassResponsibility B C >> foo ^ 42 D >> foo ^ 666 ``` Pull Up D>> foo on A (with combo box) move self...
When PullUp precondition breaks we do not propose to use transformation
When we click on code browsing we should not see this.  Can we move on and remove the old setting browser. This starts to...
Right now we get a bunch of extensions and the class is just empty.
 When I browse classDescription I see that it is extended by CodeExporter but I cannot navigate there from the extensions list.
``` CodeExporter class >> writeSourceCodeFrom: aStream toFileReference: aFileReference "Write the supplied changes to aFileReference" aFileReference ensureDelete; binaryWriteStreamDo: [ :outputStream | (ZnCharacterWriteStream on: outputStream encoding: 'utf8') nextPutAll: aStream contents ]. UIManager...
I have - a superclass with handleKey in the hook protocol - in a subclass I have a handleKey method in as yet unclassified - selecting classify does not propose...