Hello all,

Last week I did these tasks:

- Fix issue: Extract method in the superclass is not fully working #8871
<https://github.com/pharo-project/pharo/issues/8871> Now you can specify
the class where you want the method to be extracted. Check PR to know the
change <https://github.com/pharo-project/pharo/pull/8924>. You can see the
new behavior in the following video:
https://www.youtube.com/watch?v=fCCp9he8Zq0
- Add option to use scopes in refactorings. Check PR
<https://github.com/pharo-project/pharo/pull/8950> to know the change.
- Fix issue: Remove method (cmd-x) does not respect scoped mode #8638
<https://github.com/pharo-project/pharo/issues/8638>   Check PR
<https://github.com/pharo-project/pharo/pull/8950> to know the change.
- Fix issue: RBExpandReferencedPoolRefactoring refers directly to Smalltalk
globals #6510 <https://github.com/pharo-project/pharo/issues/6510>. Check PR
<https://github.com/pharo-project/pharo/pull/8959> to know the change.
- Start to fix the issue: Inline temp refactoring can create code with
different behavior. #6056
<https://github.com/pharo-project/pharo/issues/6056>. Check the changes in
this branch
<https://github.com/pharo-project/pharo/compare/Pharo9.0...Lin777:CreateCascade?expand=1>
.

Tasks for this week:

 - Correct the scope modal, when we launch a refactoring in a global mode
(current vm).
- Finish to fix: Create cascade issue
<https://github.com/pharo-project/pharo/issues/6056>.
- Fix issue: Inline senders refactoring does not correctly manage errors
#6218 <https://github.com/pharo-project/pharo/issues/6218>
- Fix issue: Incorrect message in Refactor push up with super sends #2656
<https://github.com/pharo-project/pharo/issues/2656>
<https://github.com/pharo-project/pharo/issues/8871>
- Fix issue: move to component refactoring issue.
<https://github.com/pharo-project/pharo/issues/8499>
- Fix issue: Move to package of defining class enh #8929
<https://github.com/pharo-project/pharo/issues/8929>
<https://github.com/pharo-project/pharo/issues/6218>

Regards,

Evelyn C.

Reply via email to