Skip to content

Conversation

@fouziray
Copy link
Contributor

@Ducasse
Copy link
Member

Ducasse commented Mar 1, 2025

Fixing add argument #17908

@Ducasse Ducasse requested a review from balsa-sarenac March 1, 2025 10:33
@Ducasse Ducasse changed the title Fix issue 17908 Fix issue 17908 - Rename argument Mar 1, 2025
@Ducasse
Copy link
Member

Ducasse commented Mar 1, 2025

Thank you for the fix.

self configureMessage.

refactoring isMethodDefinitionUnchanged ifTrue: [ ^ self ].
shouldEscape ifTrue: [ ^ self ]. "What is the use of this variable: shouldEscape?"
Copy link
Member

@balsa-sarenac balsa-sarenac Mar 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

User can invoke this refactoring by mistake or give up while typing new name (in requestNewMessage). If this happens, user clicks on Cancel and with this variable we propagate that cancel to escape this loop. Maybe there is a better way to do this?

@Ducasse Ducasse merged commit bc007f6 into pharo-project:Pharo13 Mar 5, 2025
1 check passed
@Ducasse
Copy link
Member

Ducasse commented Mar 5, 2025

Tx Balsa

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants