FogBugz (Case [Issue]11019) Refactoring - RBMoveMethodRefactoring should offer arguments as possible receivers

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

FogBugz (Case [Issue]11019) Refactoring - RBMoveMethodRefactoring should offer arguments as possible receivers

Pharo Issue Tracker
A FogBugz case was opened by Gisela Decuzzi.

Case ID:      11019
Title:        RBMoveMethodRefactoring should offer arguments as possible receivers
Status:       Work Needed
Category:     Enhancement
Project:      Refactoring
Area:         Misc
Priority:     5 - Fix If Time
Milestone:    Later
Assigned To:  Everyone

URL:          https://pharo.fogbugz.com/default.asp?11019

1. Open a message with parameters. Example: privateMoveMethodFor:
2. Apply the MoveMethodRefactoring
3. When choosing the receiver for the new message only offers instace variable the argument should be a possible receiver also.


You are subscribed to this case.  If you do not want to receive automatic notifications in the future, unsubscribe (https://pharo.fogbugz.com/default.asp?pre=preUnsubscribe&pg=pgEditBug&command=view&ixBug=11019) from this case.

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker