Skip to content

fix feedback to user when something goes wrong in insert superclass/subclass refactor - #19994

Open
estebanlm wants to merge 4 commits into
pharo-project:Pharo14from
estebanlm:fix-issue-19987-v2
Open

fix feedback to user when something goes wrong in insert superclass/subclass refactor#19994
estebanlm wants to merge 4 commits into
pharo-project:Pharo14from
estebanlm:fix-issue-19987-v2

Conversation

@estebanlm

@estebanlm estebanlm commented Sep 10, 2026

Copy link
Copy Markdown
Member

as there is no feedback, is sometimes confusing to not know what is happening.
this PR handles the inform to the user of things that are happening.

Fixes #19988
Fixes #19987

I also took the oportunity to caught any error happened in the refactor and transform it into an inform with an error message (most users will not do anything with a debugger other than close it with a bad feeling, and since the pre-debug window is gone, this feels horrible., so better to just send a message of what went wrong).

…efactor.

I also took the oportunity to caught any error happened in the refactor and transform it into an inform with an error message (most users will not do anythign with a debugger, and since the pre-debug window is gone, this feels horrible).
@estebanlm estebanlm changed the title fix feedback to user when something goes wrong in insert superclass refactor fix feedback to user when something goes wrong in insert superclass/subclass refactor Sep 11, 2026
@estebanlm

Copy link
Copy Markdown
Member Author

apparently the errors are unrelated

@@ -0,0 +1,11 @@
"
""Handles command !<anInteger> and return (if it exists) the command related to the number

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Esteban I do not know if this changes is wished or not.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

crap, not... that sneaked in when commiting :P

self deny: universalEnvironment isClassEnvironment.
self assert: aClassEnvironment isClassEnvironment.
self assert: aClassEnvironment packages size equals: 1.
self deny: (universalEnvironment isClassEnvironment).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We do not need the parentheses.

StRefactoringAddClassPresenterTest >> testClassNameInputIsRecordedInDriver [
| driver |

driver := presenter instVarNamed: 'driver'.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

why not using an accessor?
It makes sense that we can access the driver of a presenter.

@estebanlm estebanlm Sep 11, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

indeed. It was not me who did that !

Comment thread src/Refactoring-UI/ReInteractionDriver.class.st Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants