Manuscript (Case [Issue]22676) Refactoring - Cannot extract method with a name matching the one in a superclass being a subclassResponsibility

Classic

List

Threaded

♦

♦

Locked 1 message

Pharo Issue Tracker

Reply | Threaded

Open this post in threaded view

♦

♦

|

Manuscript (Case [Issue]22676) Refactoring - Cannot extract method with a name matching the one in a superclass being a subclassResponsibility

Pavel Krivanek edited Case 22676: Cannot extract method with a name matching the one in a superclass being a subclassResponsibility: Bug in  Refactoring: 1. Pharo Image  •  You are subscribed to this case This is the general issue of Calypso refactorings. All refactoring warnings are now displayed as errors (which is wrong) Tags changed: Added tag 'BlockingForRelease'. 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. A Manuscript case was edited by Pavel Krivanek. Case ID: 22676 Title: Cannot extract method with a name matching the one in a superclass being a subclassResponsibility Status: Work Needed Category: Bug Project: Refactoring Area: 1. Pharo Image Priority: 2 - Really Important Milestone: Pharo7.0: 2.9.2018 (Past) Assigned To: Everyone URL: https://pharo.manuscript.com/f/cases/22676 Changes: Added tag 'BlockingForRelease'. This is the general issue of Calypso refactorings. All refactoring warnings are now displayed as errors (which is wrong) You are subscribed to this case. If you do not want to receive automatic notifications in the future, unsubscribe (https://pharo.manuscript.com/default.asp?pre=preUnsubscribe&pg=pgEditBug&command=view&ixBug=22676) from this case. _______________________________________________ Pharo-bugtracker mailing list [hidden email] https://lists.gforge.inria.fr/mailman/listinfo/pharo-bugtracker