New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix so that Rename Method refactoring does not start with a disabled text input #10390
Fix so that Rename Method refactoring does not start with a disabled text input #10390
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is good to go. I added a few detailed comments which should be simple to correct, but works fine without.
Is there a way for you to add a test to make sure the error do not sneak back in? That would be really nice.
@@ -346,7 +358,7 @@ SycMethodNameEditorPresenter >> initializeWidgets [ | |||
addButton label: '+'. | |||
selectorInput text: methodName selector. | |||
previewResult label: methodName methodName. | |||
selectorInput beNotEditable. | |||
"selectorInput beNotEditable." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps this line should be deleted (not leaving code in comments)
@@ -136,6 +135,19 @@ SycMethodNameEditorPresenter class >> openOn: aMethod withInvalidArgs: aSet canR | |||
^ temp openBlockedDialogWithSpec | |||
] | |||
|
|||
{ #category : #specs } | |||
SycMethodNameEditorPresenter class >> openOn: aMethod withInvalidArgs: aSet canRenameArgs: aBoolean1 canRemoveArgs: aBoolean2 canAddArgs: aBoolean3 canEditName: aBoolean4 [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps some better argument names?
Miguel this is really annoying that we cannot use rename anymore in Pharo. |
I will integrate these changes and I hope that they work because to me I cannot use Pharo now. |
Fix for issue #10332