Pharo Issue Tracker - Manuscript (Case [Issue]22319) Refactoring - Extracting an already existing method should not raise an error!

Manuscript Notification

	Denis Kudryashov edited Case 22319: Extracting an already existing method should not raise an error! : Bug in Refactoring: 1. Pharo Image • You are subscribed to this case

I checked my fix in this scenario. It does not help because by default general Error is raised instead of RefactoringWarning. There are many other cases where default refactoring options are defined with general error.

I think refactoring engine should be modified to be based on exceptions instead of options. This way we will be able delegate them interaction with user to take decision.

	Priority: 2 – Really Important		Status: Work Needed
	Assigned to: Everyone		Milestone: Pharo7.0

Go to Case

No longer need updates? Unsubscribe from this case.

Don't want Manuscript notifications anymore? Update your preferences.

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