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

Add additional logic to MoveInstanceMethodProcessor #1537

Merged
merged 1 commit into from
Jul 24, 2024

Conversation

jjohnstn
Copy link
Contributor

  • add new MoveInstanceMethodProcessor.checkOverrideOuterMethod() that checks if a sub-class inner type of the target type calls a method with same name as moved but the method is declared in a different type so an unexpected override will occur
  • add new test to MoveInstanceMethodTests
  • fixes Bug: Move method refactoring causes changes in code behavior #1517

What it does

See issue.

How to test

See issue or new test.

Author checklist

- add new MoveInstanceMethodProcessor.checkOverrideOuterMethod()
  that checks if a sub-class inner type of the target type calls a
  method with same name as moved but the method is declared in
  a different type so an unexpected override will occur
- add new test to MoveInstanceMethodTests
- fixes eclipse-jdt#1517
@jjohnstn jjohnstn self-assigned this Jul 24, 2024
@jjohnstn jjohnstn added the bug Something isn't working label Jul 24, 2024
@jjohnstn jjohnstn added this to the 4.33 M2 milestone Jul 24, 2024
@jjohnstn jjohnstn merged commit 56e4b25 into eclipse-jdt:master Jul 24, 2024
6 of 9 checks passed
@jjohnstn jjohnstn deleted the checkmove branch July 24, 2024 19:11
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.

Bug: Move method refactoring causes changes in code behavior
1 participant