Smalltalk
›
Pharo
›
Pharo Issue Tracker
Search
everywhere
only in this topic
Advanced Search
Manuscript (Case [Issue]22319) Refactoring - Extracting an already existing method should not raise an error!
‹
Previous Topic
Next Topic
›
Classic
List
Threaded
♦
♦
Locked
1 message
Pharo Issue Tracker
Reply
|
Threaded
Open this post in threaded view
♦
♦
|
Manuscript (Case [Issue]22319) Refactoring - Extracting an already existing method should not raise an error!
Manuscript Notification
Pavel Krivanek
resolved
Case 22319
: Extracting an already existing method should not raise an error!
and assigned it to
Stephane Ducasse
:
Bug
in
Refactoring: 1. Pharo Image • You are subscribed to this case
Fixed with the latest update of Calypso
Status
changed:
Work Needed
Resolved (Fixed)
Assigned To
changed:
Everyone
Stephane Ducasse
Priority
: 2 – Really Important
Status
: Resolved (Fixed)
Assigned to
: Stephane Ducasse
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 Resolved (Fixed) and assigned to Stephane Ducasse by Pavel Krivanek. Case ID: 22319 Title: Extracting an already existing method should not raise an error! Status: Resolved (Fixed) Category: Bug Project: Refactoring Area: 1. Pharo Image Priority: 2 - Really Important Milestone: Pharo7.0: 9/2/2018 (Past) Assigned To: Stephane Ducasse URL: https://pharo.manuscript.com/f/cases/22319 Changes: Status changed from 'Work Needed' to 'Resolved (Fixed)'. Fixed with the latest update of Calypso 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=22319) 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