Smalltalk
›
Pharo
›
Pharo Issue Tracker
Search
everywhere
only in this topic
Advanced Search
Manuscript (Case [Issue]22676) Refactoring - Cannot extract method with a name matching the one in a superclass being a subclassResponsibility
‹
Previous Topic
Next Topic
›
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
Manuscript Notification
Pavel Krivanek
closed
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
Assigned To
changed:
gcotelli
CLOSED
Priority
: 2 – Really Important
Status
: Resolved (Fixed upstream)
Assigned to
: CLOSED
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 closed by Pavel Krivanek. Case ID: 22676 Title: Cannot extract method with a name matching the one in a superclass being a subclassResponsibility Status: Closed (Fixed upstream) Category: Bug Project: Refactoring Area: 1. Pharo Image Priority: 2 - Really Important Milestone: Pharo7.0: 9/2/2018 (Past) Assigned To: CLOSED URL: https://pharo.manuscript.com/f/cases/22676 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
Free forum by Nabble
Edit this page