You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, I use file path and method signature to identify methods. Method signature works well, but file path doesn't.
The git historical methods cannot be bound Java model elements (resolving binding always returns null for a method declaration), so I could not get their typeFQNs.
How can we know a git historical method is an existing method in the current source code?
The text was updated successfully, but these errors were encountered:
The git historical methods cannot be bound Java model elements (resolving binding always returns null for a method declaration), so I could not get their typeFQNs.
Of course not. That's why they are "historical." They are no longer in the project.
How can we know a git historical method is an existing method in the current source code?
Currently, I use file path and method signature to identify methods. Method signature works well, but file path doesn't.
The git historical methods cannot be bound Java model elements (resolving binding always returns null for a method declaration), so I could not get their typeFQNs.
How can we know a git historical method is an existing method in the current source code?
The text was updated successfully, but these errors were encountered: