ReplaceInitMockToOpenMock: Ensure unique name for added tearDown method #725
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@timtebeek this one is minor change. Can you please take a look. |
timtebeek
approved these changes
May 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's changed?
This pr updates the ReplaceInitMockToOpenMock recipe to avoid creating duplicate tearDown methods. Previously, the recipe would unconditionally add a tearDown method, potentially causing conflicts if one already existed in the class. The new logic checks for existing methods named tearDown and appends the next available numeric suffix (e.g., tearDown0, tearDown1, etc.) to ensure method name uniqueness.
Checklist