Skip to content
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 change method signature to recognize name collision #1767

Merged
merged 2 commits into from
Nov 6, 2024

Conversation

jjohnstn
Copy link
Contributor

@jjohnstn jjohnstn commented Nov 5, 2024

What it does

Prevents or warns about a potential rename issue in change method signature. See issue.

How to test

See issue or new test.

Author checklist

- modify ChangeSignatureProcessor to check for the case where the
  new name is already a method accessible to a location that is
  calling the old name
- make method in Checks class public to convert ICompilationUnit to
  CompilationUnit
- add new test to ChangeSignatureTests
- fixes eclipse-jdt#1751
@jjohnstn jjohnstn self-assigned this Nov 5, 2024
@jjohnstn jjohnstn added the bug Something isn't working label Nov 5, 2024
@jjohnstn jjohnstn added this to the 4.34 M3 milestone Nov 5, 2024
@jjohnstn jjohnstn merged commit 0734ebc into eclipse-jdt:master Nov 6, 2024
10 checks passed
@jjohnstn jjohnstn deleted the renamerecursion branch November 6, 2024 02:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

"Change Method Signature refactoring": Causes method recursion
1 participant